Alle Meldungen
Twin Tin Bots Meldungen
#8962: "2nd move order out of mud did not move robot. First order was given by zap."
notupdated: Die Meldung wurde automatisch geschlossen, weil es lange Zeit keine Stimmen / Kommentare dazu gab
2
Worum geht es bei dieser Meldung?
Was ist passiert? Bitte wähle unten aus
Regeln: Eine Regel des Spiels wurde nicht beachtet
Detaillierte Beschreibung
• Welcher Teil der Spielregel wurde durch die BGA-Adaption nicht beachtet?
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.• Ist der Regelverstoß in der Spielwiederholung zu sehen? Falls ja, bei welcher Zugnummer?
Yes, replay from move 80. The bug occurs at move 81 I think, or 82.• Welchen Browser benutzt du?
Google Chrome v49
Meldungshistorie
9. Jan 2018 7:40 • Cactus Tom • Der Fehler wurde von den Entwicklern noch nicht nachvollzogen:
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 • Der Fehler wurde von den Entwicklern noch nicht nachvollzogen:
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. Mär 2019 11:16 • Sourisdudesert • Die Meldung wurde automatisch geschlossen, weil es lange Zeit keine Stimmen / Kommentare dazu gab:
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. Mai 2020 15:18 • carrben12 • Die Meldung wurde automatisch geschlossen, weil es lange Zeit keine Stimmen / Kommentare dazu gab:
This is still abug.
Ergänze diese Meldung
Bitte erwähne hier alles, was bedeutsam sein könnte, um diesen Fehler nachzuvollziehen oder deinen Vorschlag zu verstehen:
- Eine weitere Tisch-ID/Zug-ID
- Konnte F5 das Problem lösen?
- Trat das Problem öfter auf? Jedes Mal? Zufällig?
- Falls du einen Screenshot dieses Fehlers hast (optimale Vorgehensweise), kannst du ihn bei Imgur.com hochladen, den Link kopieren und hier einfügen.
