All reports
framework_displayed reports
#128968: "Two colour task rule not followed"
fixed: Bug has been fixed
4
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
Section 2 of page 8 of the rulebook says
"This task requires at least 6 horizontally and/or vertically adjacent frames of
the colours shown in any combination. For example, 2 yellow frames and
4 green frames can be used. However, it is important that both colours have
a direct connection to the task. This task may also be completed by using
only one of the two shown colours. Later on, the other two tasks can also be
fulfilled when the number of adjacent frames reaches 9 or 12."
The game allows these tasks to be completed when both colours do not have a direct connection to the task.• Is the rules violation visible on game replay? If yes, at which move number?
Final move of the game• What is your browser?
MS Edge Version 126.0.2592.61 (Official build) (64-bit)
Report history
Witty_user_name • Bug has not been reproduced by delopers yet:
29. Jun 2024 22:54 • The bug has been reported before and marked as not a bug but this still seems to disagree with the rulebook
Matsumi_Elen • Bug has not been reproduced by delopers yet:
6. Aug 2024 18:12 • boardgamearena.com/archive/replay/240725-1000/?table=546596689&player=85201406&comments=85201406; The same mistake was made, I can throw off the screenshot with analysis.
vurtan • Bug has been fixed:
6. Aug 2024 23:30 • The rulebook differs from the decision the designer made as we asked him for clarification. So we implemented it in the new way.
Since we have the other more strict version where each color is treated seperately I created an option in order to change this.
Since we have the other more strict version where each color is treated seperately I created an option in order to change this.
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.