All reports
bubbleepop_displayed reports
#13968: "Bug in Yellow-power"
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
When a yellow-combo has been made, you may use the yellow power: "The player may place one of their free Bubblees in their Score Area. (A Bubblee is considered free if no Bubblee stands on top of it.)"
• Is the rules violation visible on game replay? If yes, at which move number?
In move 150, Curling uses the yellow power on a non-free Bubblee. (Takes a green, when a red is stading on top of it.)• What is your browser?
Google Chrome v78
Report history
2. Dec 2019 20:38 • HanabiGrandMaster • Bug has not been reproduced by delopers yet:
I think it's because in this stage of the game, it is allowed to have bubblees above the planet (more than 4 bubblees in a stack) without losing the game. The extra bubblees are not counted in the algorithm that determines the top bubblee.
30. May 2021 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.
26. May 2024 17:41 • gaylon • This report has been closed automatically because there was no vote/comment on it for a long time:
This bug still exists:
boardgamearena.com/gamereview?table=517183363 Move#129
"Purple power: Luca1981 sends an uncovered Bubblee to the opposing Planet"
The game allowed the wrong bubblee to be sent. The player sent the second-to-top (green) bubblee, which was covered by another (yellow) bubblee.
The bug can affect both yellow and purple powers, when a column is temporarily overfilled until a player sends a bubblee away (to their score area, or to their opponent's planet). The rules allow the player to choose any "free"/"uncovered" bubblee to send. The rules state that "A Bubblee is considered free if no Bubblee stands on top of it." The player *should* be able to send the topmost bubblee, which is temporarily overflowing from their planet. Instead, the BGA implementation lets them send the bubblee from the topmost of the four positions in the 4x5 planet grid, even though that bubblee is covered by the newly-fallen bubblee.
This bug has been reported previously, without any action/fix.
boardgamearena.com/gamereview?table=517183363 Move#129
"Purple power: Luca1981 sends an uncovered Bubblee to the opposing Planet"
The game allowed the wrong bubblee to be sent. The player sent the second-to-top (green) bubblee, which was covered by another (yellow) bubblee.
The bug can affect both yellow and purple powers, when a column is temporarily overfilled until a player sends a bubblee away (to their score area, or to their opponent's planet). The rules allow the player to choose any "free"/"uncovered" bubblee to send. The rules state that "A Bubblee is considered free if no Bubblee stands on top of it." The player *should* be able to send the topmost bubblee, which is temporarily overflowing from their planet. Instead, the BGA implementation lets them send the bubblee from the topmost of the four positions in the 4x5 planet grid, even though that bubblee is covered by the newly-fallen bubblee.
This bug has been reported previously, without any action/fix.
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.
