All reports
dronesvsseagulls_displayed reports
#78586: "nouveau premier joueur a 4 jetons à sa couleur"
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
la regle n'est pas explicite, mais il me semble que le premier joueur de la 2eme manche devrait (comme pour la 1ere manche) avoir juste 3 jetons à sa couleur.• Is the rules violation visible on game replay? If yes, at which move number?
oui, coup 24• What is your browser?
Google Chrome v108
Report history
19. Feb 2023 16:50 • OldDuckCARdGuy • Bug has not been reproduced by delopers yet:
boardgamearena.com/forum/viewtopic.php?p=135210#p135210
This discussion linked here details the same type of situation it seems.
This type of problem is game-breaking for a game of this nature.
This discussion linked here details the same type of situation it seems.
This type of problem is game-breaking for a game of this nature.
20. Apr 2023 19:29 • rcampbell04 • Bug has not been reproduced by delopers yet:
I have had this happen in Table #365066285, Move #21, Progression 33%
11. Sep 2023 16:03 • ahyangyi • Bug has not been reproduced by delopers yet:
Also happened at the second game of Table #414398748
31. Aug 2024 14:42 • JackNapis • Bug has not been reproduced by delopers yet:
Also happened with the second game of Table #556440111
According to the rules, the player who wins a round is the start player for the next round. If they also control more outposts at the start of the round, this seems like a huge advantage to them which could completely unbalance the game. I'm disappointed that this bug hasn't even been acknowledged, let alone fixed, 20 months after it was reported.
According to the rules, the player who wins a round is the start player for the next round. If they also control more outposts at the start of the round, this seems like a huge advantage to them which could completely unbalance the game. I'm disappointed that this bug hasn't even been acknowledged, let alone fixed, 20 months after it was reported.
15. Sep 2024 13:15 • vertex5 • Bug has not been reproduced by delopers yet:
Happening right now on table 561234285. Any chance of a fix while the game is still going?
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.
