Alle rapporter
Twin Tin Bots rapporter
#8962: "2nd move order out of mud did not move robot. First order was given by zap."
notupdated: Denne rapporten er stengt automatisk fordi det ikke var noen stemme / kommentar på det i lang tid
2
Hva handler denne rapporten om?
Hva har skjedd, eller hva gjelder det? Vennligst velg
Regler: en regel i spillet har ikke blitt respektert
Detaljert beskrivelse
• Hvilken del av reglene ble ikke respektert av BGA-tilpasningen
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.• Er regelbruddet tydelig i spilloggen? Hvis ja, Hvilket trekknummer?
Yes, replay from move 80. The bug occurs at move 81 I think, or 82.• Hvilken nettleser bruker du?
Google Chrome v49
Rapporthistorikk
jan. 9 th 2018 7:40 • Cactus Tom • Feilen har ikke blitt reprodusert av utviklerne enda:
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."
jan. 9 th 2018 21:10 • Cactus Tom • Feilen har ikke blitt reprodusert av utviklerne enda:
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)
mars 8 th 2019 11:16 • Sourisdudesert • Denne rapporten er stengt automatisk fordi det ikke var noen stemme / kommentar på det i lang tid:
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.
mai 29 th 2020 15:18 • carrben12 • Denne rapporten er stengt automatisk fordi det ikke var noen stemme / kommentar på det i lang tid:
This is still abug.
Legg til noe i denne rapporten
Legg til her noe som synes relevant for å reprodusere denne feilen eller forstå forslaget ditt:
- En annen bord ID / flytt ID
- Løste F5 problemet?
- Oppstod problemet gjentatte ganger? Hver gang? Tilfeldig?
- Hvis du har et skjermbilde av denne feilen (alltid lurt) kan du bruke Imgur.com for å laste det opp og kopiere inn lenken til bildet her.
