All reports
citadels_displayed reports
#83491: "Assassinated player should not be revealed"
What is this report about?
What happened ? Please select from below
Suggestion: in my opinion, the following would greatly improve the game implementation
Detailed description
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
As I recall, the rules say if the assassin kills, say, the Merchant (6, as in my game) that role should just be skipped. In this way, I (Architect, 7) don't know if the remaining player is the Warlord (8) or the assassinated Merchant (6). In my game, it shows the player's username above above the Merchant, in addition to the assassin symbol below showing the character was killed. The symbol should remain, perhaps covering the name, if that is easier to code.• What is your browser?
Google Chrome v110
Report history
14. Mar 2023 19:24 • BibleandboardGames • This suggestion has not been analyzed by delopers yet:
snipboard.io/gCHq0w.jpg
I tried to link to the rules, but the link on Z-MAN's website wasn't working.
I tried to link to the rules, but the link on Z-MAN's website wasn't working.
21. Feb 2024 8:49 • Tricuspa • This suggestion has not been analyzed by delopers yet:
Player affected is the Magician's Ability
Assassin always kills the "Role" who that player was is not announced but it could be listed after the turn is over for "guilty" conscience which I feel is another aspect of the game, perhaps an option of "Conscience"
Currently the Assassin is only listed at killing the role from my game played, and you don't see who you affected in asynchronous play.
Assassin always kills the "Role" who that player was is not announced but it could be listed after the turn is over for "guilty" conscience which I feel is another aspect of the game, perhaps an option of "Conscience"
Currently the Assassin is only listed at killing the role from my game played, and you don't see who you affected in asynchronous play.
Add something to this report
Please add here anything that seems relevant to reproduce this bug or understand your suggestion:
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appears several time? Everytime? Randomly?
- If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
