All reports
notalone_displayed reports
#75120: "detector "
notupdated: This report has been closed automatically because there was no vote/comment on it for a long time
1
What is this report about?
What happened ? Please select from below
Rules: a rule of the game has not been respected
Detailed description
• Which part of the rules was not respected by the BGA adaptation
I couldn't play Detector card to avoid Artemia token.
I had to discard my last card.• Is the rules violation visible on game replay? If yes, at which move number?
#145• What is your browser?
Google Chrome v107
Report history
3. Nov 2022 20:21 • pabula • Bug has not been reproduced by delopers yet:
I should be allowed to avoid the effect of the Artemia token and resolve my Rover card.
4. Nov 2023 12:16 • Sourisdudesert • This report has been closed automatically because there was no vote/comment on it for a long time:
Report closed automatically because it has not been upvoted or commented for a while.
Your bug has probably been fixed already, or was linked to a temporary failure of BGA service.
In any case, when filling a bug report, make sure to have an explicit title linked to the incident (ex: with error message), so other players can recognize it and vote for it.
Your bug has probably been fixed already, or was linked to a temporary failure of BGA service.
In any case, when filling a bug report, make sure to have an explicit title linked to the incident (ex: with error message), so other players can recognize it and vote for it.
3. Feb 2024 23:54 • LesserJester • This report has been closed automatically because there was no vote/comment on it for a long time:
i just had the same problem, blocked from playing detector in round 3, this is a bug and has not been fixed.
4. Feb 2024 0:10 • LesserJester • This report has been closed automatically because there was no vote/comment on it for a long time:
new bug report here. Kindly don't just close this one. There is a problem. boardgamearena.com/bug?id=113436
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.
