All reports
dronesvsseagulls_displayed reports
#114335: "Same as this report, but I'm writing it in English: "nouveau premier joueur a 4 jetons à sa couleur""
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
The rule is for the player who has 3 locations to start the match. During the second round, the game let the player with 4 locations start the match, which is highly unfair.
-
• Is the rules violation visible on game replay? If yes, at which move number?
Yes, it will be visible right at the beginning of the second match.
• What is your browser?
Google Chrome v121
Report history
Cheddarific • Bug has not been reproduced by delopers yet:
11. Feb 2024 23:39 • Not sure what caused it. I've only played this game on BGA a handful of times and it was the first time I've seen this problem.
vertex5 • Bug has not been reproduced by delopers yet:
21. Aug 2024 14:25 • Also happened in the second round at table 551357111. I think this is the only time I've seen it.
Board Game Arena • This report has been closed automatically because there was no vote/comment on it for a long time:
22. Aug 2025 12:16 • 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.