#72121: "Cancel move should be default action when clicking on ship that already moved"
Hva handler denne rapporten om?
Hva har skjedd, eller hva gjelder det? Vennligst velg
Hva har skjedd, eller hva gjelder det? Vennligst velg
Vennligst sjekk om det allerede er en rapport om samme emne
Hvis ja, vennligst STEM på denne rapporten. Rapporter med flest stemmer er gitt PRIORITET!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detaljert beskrivelse
-
• Vennligst kopier/lim inn feilmeldingen du ser på skjermen, om mulig.
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. -
• Vennligst forklar hva du ønsket å gjøre, samt hva du faktisk gjorde og hva som skjedde
• Hvilken nettleser bruker du?
Google Chrome v105
-
• Vennligst kopier / lim inn teksten som vises på engelsk i stedet for språket ditt. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Er denne teksten tilgjengelig i translation system? Hvis ja, har den blitt oversatt i mer enn 24 timer?
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. • Hvilken nettleser bruker du?
Google Chrome v105
-
• Vennligst forklar ditt forslag nøyaktig og konsistent slik at det er så enkelt som mulig å forstå hva du mener.
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. • Hvilken nettleser bruker du?
Google Chrome v105
-
• Hva ble vist på skjermen når du ble blokkert (Tom skjerm? Del av spillgrensesnittet? Feilmelding?)
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. • Hvilken nettleser bruker du?
Google Chrome v105
-
• Hvilken del av reglene ble ikke respektert av BGA-tilpasningen
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. -
• Er regelbruddet tydelig i spilloggen? Hvis ja, Hvilket trekknummer?
• Hvilken nettleser bruker du?
Google Chrome v105
-
• Hva var spillhandlingen du ønsket å gjøre?
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. -
• Hva prøvde du å gjøre for å trigge denne spillhandlingen?
-
• Hva skjer når du prøver å gjøre dette (feilmelding, meldingsstatus for meldingsfelt, ...)?
• Hvilken nettleser bruker du?
Google Chrome v105
-
• På hvilket tidspunkt i spillet oppsto problemet (hva var den daværende spillinstruksjonen)?
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. -
• Hva skjer når du forsøker å gjøre en spillhandling (feilmelding, spillstatusfeltmelding, ...)?
• Hvilken nettleser bruker du?
Google Chrome v105
-
• Vennligst beskriv visningsproblemet. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) 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. • Hvilken nettleser bruker du?
Google Chrome v105
-
• Vennligst kopier / lim inn teksten som vises på engelsk i stedet for språket ditt. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Er denne teksten tilgjengelig i translation system? Hvis ja, har den blitt oversatt i mer enn 24 timer?
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. • Hvilken nettleser bruker du?
Google Chrome v105
-
• Vennligst forklar ditt forslag nøyaktig og konsistent slik at det er så enkelt som mulig å forstå hva du mener.
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. • Hvilken nettleser bruker du?
Google Chrome v105
Rapporthistorikk
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.
Legg til noe i denne rapporten
- En annen bord ID / flytt ID
- Løste F5 problemet?
- Oppstod problemet gjentatte ganger? Hver gang? Tilfeldig?
- If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here.
