#8962: "2nd move order out of mud did not move robot. First order was given by zap."
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.
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.
-
• Please explain what you wanted to do, what you did and what happened
Yes, replay from move 80. The bug occurs at move 81 I think, or 82.
• Which browser are you using?
Google Chrome v49
-
• 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.
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 this text available in the translation system? If yes, has it been translated for more than 24 hours?
Yes, replay from move 80. The bug occurs at move 81 I think, or 82.
• Which browser are you using?
Google Chrome v49
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
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.
• Which browser are you using?
Google Chrome v49
-
• What was displayed on the screen when you were blocked (Blank screen? Part of the game interface? Error message?)
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.
• Which browser are you using?
Google Chrome v49
-
• Which part of the rules was not followed 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.
• Which browser are you using?
Google Chrome v49
-
• What was the game action you wanted to do?
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.
-
• What did you try to do to trigger this game action?
Yes, replay from move 80. The bug occurs at move 81 I think, or 82.
-
• What happened when you tried to do this (error message, game status bar message, ...)?
• Which browser are you using?
Google Chrome v49
-
• At which step of the game did the problem occur? What was the current game instruction?
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.
-
• What happened when you tried to do this game action (error message, game status bar message, ...)?
Yes, replay from move 80. The bug occurs at move 81 I think, or 82.
• Which browser are you using?
Google Chrome v49
-
• 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.
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.
• Which browser are you using?
Google Chrome v49
-
• 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.
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 this text available in the translation system? If yes, has it been translated for more than 24 hours?
Yes, replay from move 80. The bug occurs at move 81 I think, or 82.
• Which browser are you using?
Google Chrome v49
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
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.
• Which browser are you using?
Google Chrome v49
Report history
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."
boardgamegeek.com/article/27911536#27911536
(Start at the post by tomslick)
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.
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.
