#72121: "Cancel move should be default action when clicking on ship that already moved"
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.
Currently, when you are clicking on a ship you already moved, you undo that move, without any prompt form the UI.
I don't think this should be the default behavior.
Example:
I move ship A and then move ship B into the hex Ship A just vacated. Before committing my move I click ship A, which causes Ship A to back to the hex it came from. Since that was not what I wanted, I just clicked Ship A and moved it again.
This caused a collision which, of course, was not what I wanted.
At first, I thought it was a bug, but I can see that it is not a bug as such.
When first moving my ships, I was careful to move them in the right order. The confusing interaction with the UI caused me to, inadvertently, reverse the order of movement of my ships, causing the collision. -
• Please explain what you wanted to do, what you did and what happened
• Which browser are you using?
Google Chrome v105
-
• 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.
Currently, when you are clicking on a ship you already moved, you undo that move, without any prompt form the UI.
I don't think this should be the default behavior.
Example:
I move ship A and then move ship B into the hex Ship A just vacated. Before committing my move I click ship A, which causes Ship A to back to the hex it came from. Since that was not what I wanted, I just clicked Ship A and moved it again.
This caused a collision which, of course, was not what I wanted.
At first, I thought it was a bug, but I can see that it is not a bug as such.
When first moving my ships, I was careful to move them in the right order. The confusing interaction with the UI caused me to, inadvertently, reverse the order of movement of my ships, causing the collision. -
• Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
• Which browser are you using?
Google Chrome v105
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
Currently, when you are clicking on a ship you already moved, you undo that move, without any prompt form the UI.
I don't think this should be the default behavior.
Example:
I move ship A and then move ship B into the hex Ship A just vacated. Before committing my move I click ship A, which causes Ship A to back to the hex it came from. Since that was not what I wanted, I just clicked Ship A and moved it again.
This caused a collision which, of course, was not what I wanted.
At first, I thought it was a bug, but I can see that it is not a bug as such.
When first moving my ships, I was careful to move them in the right order. The confusing interaction with the UI caused me to, inadvertently, reverse the order of movement of my ships, causing the collision. • Which browser are you using?
Google Chrome v105
-
• What was displayed on the screen when you were blocked (Blank screen? Part of the game interface? Error message?)
Currently, when you are clicking on a ship you already moved, you undo that move, without any prompt form the UI.
I don't think this should be the default behavior.
Example:
I move ship A and then move ship B into the hex Ship A just vacated. Before committing my move I click ship A, which causes Ship A to back to the hex it came from. Since that was not what I wanted, I just clicked Ship A and moved it again.
This caused a collision which, of course, was not what I wanted.
At first, I thought it was a bug, but I can see that it is not a bug as such.
When first moving my ships, I was careful to move them in the right order. The confusing interaction with the UI caused me to, inadvertently, reverse the order of movement of my ships, causing the collision. • Which browser are you using?
Google Chrome v105
-
• Which part of the rules was not followed by the BGA adaptation?
Currently, when you are clicking on a ship you already moved, you undo that move, without any prompt form the UI.
I don't think this should be the default behavior.
Example:
I move ship A and then move ship B into the hex Ship A just vacated. Before committing my move I click ship A, which causes Ship A to back to the hex it came from. Since that was not what I wanted, I just clicked Ship A and moved it again.
This caused a collision which, of course, was not what I wanted.
At first, I thought it was a bug, but I can see that it is not a bug as such.
When first moving my ships, I was careful to move them in the right order. The confusing interaction with the UI caused me to, inadvertently, reverse the order of movement of my ships, causing the collision. -
• Is the rules violation visible on game replay? If yes, at which move number?
• Which browser are you using?
Google Chrome v105
-
• What was the game action you wanted to do?
Currently, when you are clicking on a ship you already moved, you undo that move, without any prompt form the UI.
I don't think this should be the default behavior.
Example:
I move ship A and then move ship B into the hex Ship A just vacated. Before committing my move I click ship A, which causes Ship A to back to the hex it came from. Since that was not what I wanted, I just clicked Ship A and moved it again.
This caused a collision which, of course, was not what I wanted.
At first, I thought it was a bug, but I can see that it is not a bug as such.
When first moving my ships, I was careful to move them in the right order. The confusing interaction with the UI caused me to, inadvertently, reverse the order of movement of my ships, causing the collision. -
• What did you try to do to trigger this game action?
-
• What happened when you tried to do this (error message, game status bar message, ...)?
• Which browser are you using?
Google Chrome v105
-
• At which step of the game did the problem occur? What was the current game instruction?
Currently, when you are clicking on a ship you already moved, you undo that move, without any prompt form the UI.
I don't think this should be the default behavior.
Example:
I move ship A and then move ship B into the hex Ship A just vacated. Before committing my move I click ship A, which causes Ship A to back to the hex it came from. Since that was not what I wanted, I just clicked Ship A and moved it again.
This caused a collision which, of course, was not what I wanted.
At first, I thought it was a bug, but I can see that it is not a bug as such.
When first moving my ships, I was careful to move them in the right order. The confusing interaction with the UI caused me to, inadvertently, reverse the order of movement of my ships, causing the collision. -
• What happened when you tried to do this game action (error message, game status bar message, ...)?
• Which browser are you using?
Google Chrome v105
-
• 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.
Currently, when you are clicking on a ship you already moved, you undo that move, without any prompt form the UI.
I don't think this should be the default behavior.
Example:
I move ship A and then move ship B into the hex Ship A just vacated. Before committing my move I click ship A, which causes Ship A to back to the hex it came from. Since that was not what I wanted, I just clicked Ship A and moved it again.
This caused a collision which, of course, was not what I wanted.
At first, I thought it was a bug, but I can see that it is not a bug as such.
When first moving my ships, I was careful to move them in the right order. The confusing interaction with the UI caused me to, inadvertently, reverse the order of movement of my ships, causing the collision. • Which browser are you using?
Google Chrome v105
-
• 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.
Currently, when you are clicking on a ship you already moved, you undo that move, without any prompt form the UI.
I don't think this should be the default behavior.
Example:
I move ship A and then move ship B into the hex Ship A just vacated. Before committing my move I click ship A, which causes Ship A to back to the hex it came from. Since that was not what I wanted, I just clicked Ship A and moved it again.
This caused a collision which, of course, was not what I wanted.
At first, I thought it was a bug, but I can see that it is not a bug as such.
When first moving my ships, I was careful to move them in the right order. The confusing interaction with the UI caused me to, inadvertently, reverse the order of movement of my ships, causing the collision. -
• Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
• Which browser are you using?
Google Chrome v105
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
Currently, when you are clicking on a ship you already moved, you undo that move, without any prompt form the UI.
I don't think this should be the default behavior.
Example:
I move ship A and then move ship B into the hex Ship A just vacated. Before committing my move I click ship A, which causes Ship A to back to the hex it came from. Since that was not what I wanted, I just clicked Ship A and moved it again.
This caused a collision which, of course, was not what I wanted.
At first, I thought it was a bug, but I can see that it is not a bug as such.
When first moving my ships, I was careful to move them in the right order. The confusing interaction with the UI caused me to, inadvertently, reverse the order of movement of my ships, causing the collision. • Which browser are you using?
Google Chrome v105
Report history
When clicking a ship you have already moved, but not committed, don´t automatically cancel that move, but display a "cancel move" button instead (or something similar).
Ships are just moved in order you move them.
If you cancel one move and move again, that move will be in last.
I let players to vote for that suggestion or not.
"Cancel move should NOT be default action when clicking on ship that already moved"
This other suggestion:
boardgamearena.com/bug?id=64967
... is regarding the same problem, and the solution that he suggests is actually better than mine.
I suggest you implement that instead.
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.
