All reports
senet_displayed reports
#31322: "Premium members can choose white as favourite colour, white always starts the game = unfair"
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 starting player is supposed to be random, but if premium member has chosen white as their favourite colour, they get to start the game. Depending on game strategy, this may give unfair advantage. This still happened at least week or so back. I noticed this accidentally, since I had white as favourite colour when I still had premium account.• Is the rules violation visible on game replay? If yes, at which move number?
No, the table is just random game table so I can report this bug. It is not related to this issue.• What is your browser?
Google Chrome v80
Report history
Murrur • Bug has not been reproduced by delopers yet:
5. Jan 2021 23:46 • I hope the starting player is soon randomized, if it hasn't been fixed yet :)
Sourisdudesert • This report has been closed automatically because there was no vote/comment on it for a long time:
6. Jan 2022 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.