All reports
twintinbots_displayed reports
#31610: "My bot didn't move out of mud with 2 forward moves-"
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
In order to meve out of mud, the bot needs 2 forward moves.
My bot had "forward+zap" + "forward". But after zapping it says again "robot B forward is ignored because of mud"• Is the rules violation visible on game replay? If yes, at which move number?
Move 81.• What is your browser?
Google Chrome v87
Report history
10. Jan 2021 7:33 • Silvermiikka • Bug has not been reproduced by delopers yet:
My robot B was standing in mud. It made a forward+zap, couldn't move and zapped turning the other robot, and then my robot had 2nd forward and it should have moved pushing the other robot forward.
The game has not ended yet.
Waiting for thw next player.
imgur.com/a/JoEq2Ng
Screenshot after my move.
The game has not ended yet.
Waiting for thw next player.
imgur.com/a/JoEq2Ng
Screenshot after my move.
10. Jan 2021 7:36 • Silvermiikka • Bug has not been reproduced by delopers yet:
In the screenshot you can see the placement of the bots.
And in the right column you can see the latest moves, that movw forward was ignored by mud 2 times.
And in the right column you can see the latest moves, that movw forward was ignored by mud 2 times.
10. Jan 2021 20:23 • Silvermiikka • Bug has not been reproduced by delopers yet:
Now it happened again on my next turn, 89-90
So it is definitely a bug.
So it is definitely a bug.
15. Dec 2022 13:48 • pabula • Bug has not been reproduced by delopers yet:
zap for move is not working with mud.
this bug is ignored by the dev for a long time.
the same issue here:
boardgamearena.com/3/twintinbots?table=325683420
#123
this bug is ignored by the dev for a long time.
the same issue here:
boardgamearena.com/3/twintinbots?table=325683420
#123
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.
