#64967: "Provide SOME warning that you are going to collide before finishing the movement phase"
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.
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 -
• Vennligst forklar hva du ønsket å gjøre, samt hva du faktisk gjorde og hva som skjedde
• Hvilken nettleser bruker du?
Google Chrome v101
-
• Vennligst kopier / lim inn teksten som vises på engelsk i stedet for språket ditt. 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.
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 -
• Er denne teksten tilgjengelig i translation system? Hvis ja, har den blitt oversatt i mer enn 24 timer?
• Hvilken nettleser bruker du?
Google Chrome v101
-
• Vennligst forklar ditt forslag nøyaktig og konsistent slik at det er så enkelt som mulig å forstå hva du mener.
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 • Hvilken nettleser bruker du?
Google Chrome v101
-
• Hva ble vist på skjermen når du ble blokkert (Tom skjerm? Del av spillgrensesnittet? Feilmelding?)
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 • Hvilken nettleser bruker du?
Google Chrome v101
-
• Hvilken del av reglene ble ikke respektert av BGA-tilpasningen
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 -
• Er regelbruddet tydelig i spilloggen? Hvis ja, Hvilket trekknummer?
• Hvilken nettleser bruker du?
Google Chrome v101
-
• Hva var spillhandlingen du ønsket å gjøre?
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 -
• 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 v101
-
• På hvilket tidspunkt i spillet oppsto problemet (hva var den daværende spillinstruksjonen)?
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 -
• Hva skjer når du forsøker å gjøre en spillhandling (feilmelding, spillstatusfeltmelding, ...)?
• Hvilken nettleser bruker du?
Google Chrome v101
-
• Vennligst beskriv visningsproblemet. 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.
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 • Hvilken nettleser bruker du?
Google Chrome v101
-
• Vennligst kopier / lim inn teksten som vises på engelsk i stedet for språket ditt. 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.
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 -
• Er denne teksten tilgjengelig i translation system? Hvis ja, har den blitt oversatt i mer enn 24 timer?
• Hvilken nettleser bruker du?
Google Chrome v101
-
• Vennligst forklar ditt forslag nøyaktig og konsistent slik at det er så enkelt som mulig å forstå hva du mener.
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 • Hvilken nettleser bruker du?
Google Chrome v101
Rapporthistorikk
Legg til noe i denne rapporten
- 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.
