All reports
onda_displayed reports
#127786: "A player wins the trick by playing a pair of 2's, although it was possible to play a pair or 1's"
fixed: Bug has been fixed
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
In the first round of the game, in the second trick, FlavienM turned the tide and played a pair of 2's (Move 13th).
Both cartmasterb and Shobu could have beaten the pair of 2's, but their turn was skipped and FlavienM automatically won the trick, so their turn should not have been skipped.• Is the rules violation visible on game replay? If yes, at which move number?
13• What is your browser?
Google Chrome v125
Report history
18. Jun 2024 22:17 • bardhu • Bug has not been reproduced by delopers yet:
I'm not sure what caused the bug, I'd try the following situation:
Bomb of the trick: Pair
Tide: High
Player 1: Opens the trick with a pair
Player 2: Follows the trick by playing a Higher Pair
Player 3: Uses a wild to turn the tide and plays a pair of two
Player 2 should have a 1 in hand and a wild available
Player 3 should have two 1's in hand
Bomb of the trick: Pair
Tide: High
Player 1: Opens the trick with a pair
Player 2: Follows the trick by playing a Higher Pair
Player 3: Uses a wild to turn the tide and plays a pair of two
Player 2 should have a 1 in hand and a wild available
Player 3 should have two 1's in hand
18. Jun 2024 22:19 • bardhu • Bug has not been reproduced by delopers yet:
Both cartmasterb and Shobu could have beaten the pair of 1's*
19. Jun 2024 1:50 • bardhu • Bug has not been reproduced by delopers yet:
Fixing a typo on the situation described
Player 1 should have a 1 in hand and a wild available
Player 2 should have two 1's in hand
Player 1 should have a 1 in hand and a wild available
Player 2 should have two 1's in hand
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.
