#64967: "Provide SOME warning that you are going to collide before finishing the movement phase"
Vad handlar denna rapport om?
Vad hände? Välj från alternativen nedan
Vad hände? Välj från alternativen nedan
Vänligen kontrollera om det redan finns en rapport om samma ämne
Om detta stämmer, RÖSTA på denna rapport. Rapporterna med flest röster har PRIORITET!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detaljerad beskrivning
-
• Var vänlig klipp och klistra in felmeddelandet du ser på skärmen, om något.
During the Talon movement phase around step 93, I moved all of my ships safely first, then when looking around the map, I accidentally clicked on DD Stalker which sent it back into the hex it came from. So I repeated the move and clicked ok...Suddenly Stalker and Freedom both took damage from the collision, which shouldn't have happened since I moved them in an order that meant they wouldn't collide.
Presumably by repeating the movement for DD Stalker it moved it's position in the movement queue and caused the collision to happen. This was really annoying and unexpected since that wasn't how I thought I'd moved them. I understand why it treated it that way but a simple warning that I was about to suffer a collision would have prevented it. I think that's less impactful than removing the 'click to undo' which is actually a nice interface -
• Varsågod och förklara vad du ville göra, vad du gjorde och vad som hände
• Vad har du för webbläsare?
Google Chrome v101
-
• Var vänlig kopiera/klistra in texten på engelska istället för ditt eget språk. 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. Är denna text tillgänglig i översättningssystemet? I så fall, var det mer än 24 timmar sedan den översattes?
During the Talon movement phase around step 93, I moved all of my ships safely first, then when looking around the map, I accidentally clicked on DD Stalker which sent it back into the hex it came from. So I repeated the move and clicked ok...Suddenly Stalker and Freedom both took damage from the collision, which shouldn't have happened since I moved them in an order that meant they wouldn't collide.
Presumably by repeating the movement for DD Stalker it moved it's position in the movement queue and caused the collision to happen. This was really annoying and unexpected since that wasn't how I thought I'd moved them. I understand why it treated it that way but a simple warning that I was about to suffer a collision would have prevented it. I think that's less impactful than removing the 'click to undo' which is actually a nice interface • Vad har du för webbläsare?
Google Chrome v101
-
• Vänligen förklara ditt förslag exakt och koncist så att det är så enkelt som möjligt att förstå vad du menar.
During the Talon movement phase around step 93, I moved all of my ships safely first, then when looking around the map, I accidentally clicked on DD Stalker which sent it back into the hex it came from. So I repeated the move and clicked ok...Suddenly Stalker and Freedom both took damage from the collision, which shouldn't have happened since I moved them in an order that meant they wouldn't collide.
Presumably by repeating the movement for DD Stalker it moved it's position in the movement queue and caused the collision to happen. This was really annoying and unexpected since that wasn't how I thought I'd moved them. I understand why it treated it that way but a simple warning that I was about to suffer a collision would have prevented it. I think that's less impactful than removing the 'click to undo' which is actually a nice interface • Vad har du för webbläsare?
Google Chrome v101
-
• Vad visades på skärmen när du blockerades (Blank skärm? Del av spelets användargränssnitt? Felmeddelande?)?
During the Talon movement phase around step 93, I moved all of my ships safely first, then when looking around the map, I accidentally clicked on DD Stalker which sent it back into the hex it came from. So I repeated the move and clicked ok...Suddenly Stalker and Freedom both took damage from the collision, which shouldn't have happened since I moved them in an order that meant they wouldn't collide.
Presumably by repeating the movement for DD Stalker it moved it's position in the movement queue and caused the collision to happen. This was really annoying and unexpected since that wasn't how I thought I'd moved them. I understand why it treated it that way but a simple warning that I was about to suffer a collision would have prevented it. I think that's less impactful than removing the 'click to undo' which is actually a nice interface • Vad har du för webbläsare?
Google Chrome v101
-
• Vilken del av reglerna respekterades inte av BGA-adaptionen?
During the Talon movement phase around step 93, I moved all of my ships safely first, then when looking around the map, I accidentally clicked on DD Stalker which sent it back into the hex it came from. So I repeated the move and clicked ok...Suddenly Stalker and Freedom both took damage from the collision, which shouldn't have happened since I moved them in an order that meant they wouldn't collide.
Presumably by repeating the movement for DD Stalker it moved it's position in the movement queue and caused the collision to happen. This was really annoying and unexpected since that wasn't how I thought I'd moved them. I understand why it treated it that way but a simple warning that I was about to suffer a collision would have prevented it. I think that's less impactful than removing the 'click to undo' which is actually a nice interface -
• Är regelbrottet synligt i återuppspelning? Om ja, vilket nummer är det på draget?
• Vad har du för webbläsare?
Google Chrome v101
-
• Vilken spelhandling ville du göra?
During the Talon movement phase around step 93, I moved all of my ships safely first, then when looking around the map, I accidentally clicked on DD Stalker which sent it back into the hex it came from. So I repeated the move and clicked ok...Suddenly Stalker and Freedom both took damage from the collision, which shouldn't have happened since I moved them in an order that meant they wouldn't collide.
Presumably by repeating the movement for DD Stalker it moved it's position in the movement queue and caused the collision to happen. This was really annoying and unexpected since that wasn't how I thought I'd moved them. I understand why it treated it that way but a simple warning that I was about to suffer a collision would have prevented it. I think that's less impactful than removing the 'click to undo' which is actually a nice interface -
• Vad försöker du göra för att sätta igång denna spelmekaniken?
-
• Vad hände när du försökte göra det här (felmeddelande, meddelande i spelstatusrad, ...)?
• Vad har du för webbläsare?
Google Chrome v101
-
• På vilket steg i spelet kom felet (vad var den aktuella instruktionen från spelet)?
During the Talon movement phase around step 93, I moved all of my ships safely first, then when looking around the map, I accidentally clicked on DD Stalker which sent it back into the hex it came from. So I repeated the move and clicked ok...Suddenly Stalker and Freedom both took damage from the collision, which shouldn't have happened since I moved them in an order that meant they wouldn't collide.
Presumably by repeating the movement for DD Stalker it moved it's position in the movement queue and caused the collision to happen. This was really annoying and unexpected since that wasn't how I thought I'd moved them. I understand why it treated it that way but a simple warning that I was about to suffer a collision would have prevented it. I think that's less impactful than removing the 'click to undo' which is actually a nice interface -
• Vad hände när du försökte utföra en spelhandling (felmeddelande, meddelande i spelstatusrad, ...)?
• Vad har du för webbläsare?
Google Chrome v101
-
• Vänligen 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.
During the Talon movement phase around step 93, I moved all of my ships safely first, then when looking around the map, I accidentally clicked on DD Stalker which sent it back into the hex it came from. So I repeated the move and clicked ok...Suddenly Stalker and Freedom both took damage from the collision, which shouldn't have happened since I moved them in an order that meant they wouldn't collide.
Presumably by repeating the movement for DD Stalker it moved it's position in the movement queue and caused the collision to happen. This was really annoying and unexpected since that wasn't how I thought I'd moved them. I understand why it treated it that way but a simple warning that I was about to suffer a collision would have prevented it. I think that's less impactful than removing the 'click to undo' which is actually a nice interface • Vad har du för webbläsare?
Google Chrome v101
-
• Var vänlig kopiera/klistra in texten på engelska istället för ditt eget språk. 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. Är denna text tillgänglig i översättningssystemet? I så fall, var det mer än 24 timmar sedan den översattes?
During the Talon movement phase around step 93, I moved all of my ships safely first, then when looking around the map, I accidentally clicked on DD Stalker which sent it back into the hex it came from. So I repeated the move and clicked ok...Suddenly Stalker and Freedom both took damage from the collision, which shouldn't have happened since I moved them in an order that meant they wouldn't collide.
Presumably by repeating the movement for DD Stalker it moved it's position in the movement queue and caused the collision to happen. This was really annoying and unexpected since that wasn't how I thought I'd moved them. I understand why it treated it that way but a simple warning that I was about to suffer a collision would have prevented it. I think that's less impactful than removing the 'click to undo' which is actually a nice interface • Vad har du för webbläsare?
Google Chrome v101
-
• Vänligen förklara ditt förslag exakt och koncist så att det är så enkelt som möjligt att förstå vad du menar.
During the Talon movement phase around step 93, I moved all of my ships safely first, then when looking around the map, I accidentally clicked on DD Stalker which sent it back into the hex it came from. So I repeated the move and clicked ok...Suddenly Stalker and Freedom both took damage from the collision, which shouldn't have happened since I moved them in an order that meant they wouldn't collide.
Presumably by repeating the movement for DD Stalker it moved it's position in the movement queue and caused the collision to happen. This was really annoying and unexpected since that wasn't how I thought I'd moved them. I understand why it treated it that way but a simple warning that I was about to suffer a collision would have prevented it. I think that's less impactful than removing the 'click to undo' which is actually a nice interface • Vad har du för webbläsare?
Google Chrome v101
Rapporthistorik
Lägg till något till denna rapport
- Ett annat spelbords-ID / drag-ID
- Löste F5 problemet?
- Uppträdde problemet flera gånger? Varje gång? Slumpmässigt?
- 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.
