All reports
ruhr_displayed reports
#76400: "Mayor final scoring with more than 10 coins reduces to 10"
notupdated: This report has been closed automatically because there was no vote/comment on it for a long time
2
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
In the Rules, the amount of money is not limited and same is for the Mayor victory points. In Game #320068598 final scoring, three players had more than 10 coins and so should win respective points. Instead, all gained only 10 points.
Additionally, in log the wrong player names have been displayed when reducing the money.• Is the rules violation visible on game replay? If yes, at which move number?
Yes, final scoring.• What is your browser?
Google Chrome v107
Report history
23. Nov 2022 22:08 • LeBörsch • Bug has not been reproduced by delopers yet:
Sorry, found related rule. Item can be closed.
21. Feb 2023 17:43 • Hubblebub • Bug has not been reproduced by delopers yet:
I just had exactly the same thing happen in my game - spent whole game playing big money strategy only for this to happen - very annoying
Table #343462118
Move #214
Progression 92%
Table #343462118
Move #214
Progression 92%
22. Feb 2024 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.
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.
