All reports
twintinbots_displayed reports
#8962: "2nd move order out of mud did not move robot. First order was given by zap."
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 robot is in mud, only its first move order is to be ignored, and the second should move it out of the mud, even if there was a turn in between.• Is the rules violation visible on game replay? If yes, at which move number?
Yes, replay from move 80. The bug occurs at move 81 I think, or 82.• What is your browser?
Google Chrome v49
Report history
9. Jan 2018 7:40 • Cactus Tom • Bug has not been reproduced by delopers yet:
For this turn, the two robots begin in adjacent cells; robot B is in the mud.
Robot A executes: turn right, zap (turn right), zap (move forward)
Robot B executes: turn right, forward & grab (white tile), drop
Both forward orders resulted in the message "Robot B forward is ignored because of the mud"
I haven't encountered this issue before, so I don't know if it is because I have interpreted the rules differently from the implementor, or because the first move order was given by a zap, or because the second move order was on a white tile, or the intervening turn order, or some combination of these. Perhaps other players will comment and narrow this down.
Relevant quotes from the English version of the rulebook:
"Mud has no memory : should a robot start his turn in the Mud,
it will need two Forward moves to get out even if one was
ignored on the previous turn."
Note that the rules are consistent about referring to a player's turn as
reprogramming both robots and executing both programs.
"Example 2 : A Robot starts his turn in a Mud hex. His program
is 'Forward 1x', 'Turn Left', 'Forward 1x'. The first Forward is
ignored, then the Robot Turns and moves out of the mud."
Robot A executes: turn right, zap (turn right), zap (move forward)
Robot B executes: turn right, forward & grab (white tile), drop
Both forward orders resulted in the message "Robot B forward is ignored because of the mud"
I haven't encountered this issue before, so I don't know if it is because I have interpreted the rules differently from the implementor, or because the first move order was given by a zap, or because the second move order was on a white tile, or the intervening turn order, or some combination of these. Perhaps other players will comment and narrow this down.
Relevant quotes from the English version of the rulebook:
"Mud has no memory : should a robot start his turn in the Mud,
it will need two Forward moves to get out even if one was
ignored on the previous turn."
Note that the rules are consistent about referring to a player's turn as
reprogramming both robots and executing both programs.
"Example 2 : A Robot starts his turn in a Mud hex. His program
is 'Forward 1x', 'Turn Left', 'Forward 1x'. The first Forward is
ignored, then the Robot Turns and moves out of the mud."
9. Jan 2018 21:10 • Cactus Tom • Bug has not been reproduced by delopers yet:
Since I felt the rules weren't completely explicit about whether a zap by the other robot counts as the same turn, I asked for clarification on BGG. According to the publisher, it does. Here is the link:
boardgamegeek.com/article/27911536#27911536
(Start at the post by tomslick)
boardgamegeek.com/article/27911536#27911536
(Start at the post by tomslick)
8. Mar 2019 11: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.
29. May 2020 15:18 • carrben12 • This report has been closed automatically because there was no vote/comment on it for a long time:
This is still abug.
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.
