All reports
ancientknowledge_displayed reports
#115506: "Game gives a false warning when excavating using Kensington Runestone's ability"
What is this report about?
What happened ? Please select from below
Display bug: some game information displayed was wrong (with no important consequence on the game)
Detailed description
• Please describe the display issue. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
Normally, the game gives warning any time you're about to do anything that can't be undone, which includes any time players are about to draw cards. Kensington Runestone has an ability in which, when excavating, instead of drawing cards, they can archive knowledge. However, when using this ability, the game gives a warning on rotating the cards, then offers the player the choice between drawing and archiving. Drawing creates a second warning, whereas archiving shouldn't create an undoable situation in the first place, so the game shouldn't generate this first warning at all. I feel like this is misleading, because it suggests a player is about to perform an unintended action.• What is your browser?
Google Chrome v121
Report history
Octrinity • Bug has not been reproduced by delopers yet:
23. Feb 2024 5:40 • I didn't think ahead to track the move number, but I do remember both scenarios (archiving knowledge and drawing as normal) happened in this game after I played Kensington Runestone.
majdi7 • Bug has not been reproduced by delopers yet:
23. Feb 2024 5:50 • en.9.boardgamearena.com/ancientknowledge?table=478682622
Happened in my game too. I don't get move number on mobile but it's about 60% through the game. Link above.
Happened in my game too. I don't get move number on mobile but it's about 60% through the game. Link above.
majdi7 • Bug has not been reproduced by delopers yet:
23. Feb 2024 6:18 • Happens again in same game with excavation turn number 637 - 638
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.