#24670: "After Mayhem, multiple bricks should be eligible to fall"
What is this report about?
What happened? Please select from below
What happened? Please select from below
Please check if there is already a report on the same subject
If yes, please VOTE for this report. Reports with the most votes are given PRIORITY!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detailed description
-
• Please copy/paste the error message you see on your screen, if applicable.
After incendiary mayhem, you can easily have a situation where multiple bricks lack any bricks underneath. Since the rules offer no guidance as to which one should be the first to fall, if I was playing this in the real world, I'd say the player can pick which brick falls first. But in the bga implementation, the app picks which one falls.
I think you need to add a lot of new rules to cover this, or (much better) simply allow the player to decide. I propose this: if, after mayhem, there are multiple candidates to fall, limn all potential falling bricks and let the player pick which one falls. -
• Please explain what you wanted to do, what you did and what happened
72, maybe -- I can never remember how to do a replay days later and don't see it in the bga faq.
• Which browser are you using?
Google Chrome v85
-
• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
After incendiary mayhem, you can easily have a situation where multiple bricks lack any bricks underneath. Since the rules offer no guidance as to which one should be the first to fall, if I was playing this in the real world, I'd say the player can pick which brick falls first. But in the bga implementation, the app picks which one falls.
I think you need to add a lot of new rules to cover this, or (much better) simply allow the player to decide. I propose this: if, after mayhem, there are multiple candidates to fall, limn all potential falling bricks and let the player pick which one falls. -
• Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
72, maybe -- I can never remember how to do a replay days later and don't see it in the bga faq.
• Which browser are you using?
Google Chrome v85
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
After incendiary mayhem, you can easily have a situation where multiple bricks lack any bricks underneath. Since the rules offer no guidance as to which one should be the first to fall, if I was playing this in the real world, I'd say the player can pick which brick falls first. But in the bga implementation, the app picks which one falls.
I think you need to add a lot of new rules to cover this, or (much better) simply allow the player to decide. I propose this: if, after mayhem, there are multiple candidates to fall, limn all potential falling bricks and let the player pick which one falls. • Which browser are you using?
Google Chrome v85
-
• What was displayed on the screen when you were blocked (Blank screen? Part of the game interface? Error message?)
After incendiary mayhem, you can easily have a situation where multiple bricks lack any bricks underneath. Since the rules offer no guidance as to which one should be the first to fall, if I was playing this in the real world, I'd say the player can pick which brick falls first. But in the bga implementation, the app picks which one falls.
I think you need to add a lot of new rules to cover this, or (much better) simply allow the player to decide. I propose this: if, after mayhem, there are multiple candidates to fall, limn all potential falling bricks and let the player pick which one falls. • Which browser are you using?
Google Chrome v85
-
• Which part of the rules was not followed by the BGA adaptation?
After incendiary mayhem, you can easily have a situation where multiple bricks lack any bricks underneath. Since the rules offer no guidance as to which one should be the first to fall, if I was playing this in the real world, I'd say the player can pick which brick falls first. But in the bga implementation, the app picks which one falls.
I think you need to add a lot of new rules to cover this, or (much better) simply allow the player to decide. I propose this: if, after mayhem, there are multiple candidates to fall, limn all potential falling bricks and let the player pick which one falls. -
• Is the rules violation visible on game replay? If yes, at which move number?
72, maybe -- I can never remember how to do a replay days later and don't see it in the bga faq.
• Which browser are you using?
Google Chrome v85
-
• What was the game action you wanted to do?
After incendiary mayhem, you can easily have a situation where multiple bricks lack any bricks underneath. Since the rules offer no guidance as to which one should be the first to fall, if I was playing this in the real world, I'd say the player can pick which brick falls first. But in the bga implementation, the app picks which one falls.
I think you need to add a lot of new rules to cover this, or (much better) simply allow the player to decide. I propose this: if, after mayhem, there are multiple candidates to fall, limn all potential falling bricks and let the player pick which one falls. -
• What did you try to do to trigger this game action?
72, maybe -- I can never remember how to do a replay days later and don't see it in the bga faq.
-
• What happened when you tried to do this (error message, game status bar message, ...)?
• Which browser are you using?
Google Chrome v85
-
• At which step of the game did the problem occur? What was the current game instruction?
After incendiary mayhem, you can easily have a situation where multiple bricks lack any bricks underneath. Since the rules offer no guidance as to which one should be the first to fall, if I was playing this in the real world, I'd say the player can pick which brick falls first. But in the bga implementation, the app picks which one falls.
I think you need to add a lot of new rules to cover this, or (much better) simply allow the player to decide. I propose this: if, after mayhem, there are multiple candidates to fall, limn all potential falling bricks and let the player pick which one falls. -
• What happened when you tried to do this game action (error message, game status bar message, ...)?
72, maybe -- I can never remember how to do a replay days later and don't see it in the bga faq.
• Which browser are you using?
Google Chrome v85
-
• Please describe the display issue. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
After incendiary mayhem, you can easily have a situation where multiple bricks lack any bricks underneath. Since the rules offer no guidance as to which one should be the first to fall, if I was playing this in the real world, I'd say the player can pick which brick falls first. But in the bga implementation, the app picks which one falls.
I think you need to add a lot of new rules to cover this, or (much better) simply allow the player to decide. I propose this: if, after mayhem, there are multiple candidates to fall, limn all potential falling bricks and let the player pick which one falls. • Which browser are you using?
Google Chrome v85
-
• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
After incendiary mayhem, you can easily have a situation where multiple bricks lack any bricks underneath. Since the rules offer no guidance as to which one should be the first to fall, if I was playing this in the real world, I'd say the player can pick which brick falls first. But in the bga implementation, the app picks which one falls.
I think you need to add a lot of new rules to cover this, or (much better) simply allow the player to decide. I propose this: if, after mayhem, there are multiple candidates to fall, limn all potential falling bricks and let the player pick which one falls. -
• Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
72, maybe -- I can never remember how to do a replay days later and don't see it in the bga faq.
• Which browser are you using?
Google Chrome v85
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
After incendiary mayhem, you can easily have a situation where multiple bricks lack any bricks underneath. Since the rules offer no guidance as to which one should be the first to fall, if I was playing this in the real world, I'd say the player can pick which brick falls first. But in the bga implementation, the app picks which one falls.
I think you need to add a lot of new rules to cover this, or (much better) simply allow the player to decide. I propose this: if, after mayhem, there are multiple candidates to fall, limn all potential falling bricks and let the player pick which one falls. • Which browser are you using?
Google Chrome v85
Report history
Example:
BEFORE ADDING COALS TO SPOT ***:
Stn20
W10 W10
*** Str5 Str5 Str5
W20 W20 W20 W20 W20
i'd need a much more complex example to show why it would matter, but if the top 10 stones were falling four levels or so, you'd have a large range of places for things to end up, which could be useful in managing building regulations and triggering a curse at the end of the turn.
In the case you describe, the written rules are the actual problem - they are not clear enough on this point.
The idea is that you always check the pyramid from top to bottom, and in each row from left to right. The written rules state this explicitly for mayhem, but do not state it explicitly for the empty fall situation. In fact, they kinda miss the whole empty fall situation (where no bricks are under another one). Those situations are resolved first, but also from top to bottom, left to right - just like the BGA program does.
I will look at the rules and try to make it clearer.
Anyways, if you do not like this rule for you and your friends, you can always house rule your physical copy as much as you like. :-) To be honest: I hardly own any board game that I have not house ruled in some way.
Add to this report
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appear several times? Every time? 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.
