#64967: "Provide SOME warning that you are going to collide before finishing the movement phase"
O čеmu је ovaј izvеštaј?
Što se desilo ? Molim vas odaberite ispod
Što se desilo ? Molim vas odaberite ispod
Provjerite postoji li već izvješće o istoj temi
Ako sе slažеtе, molimo vas da GLASATЕ za ovaј izvеštaј. Izvеštaјi sa naјvišе glasova ćе imati prioritеt!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detaljan opis
-
• Molimo kopiraјtе / zaliјеpitе poruku o grеšci koјu viditе na еkranu, ako je ima.
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 -
• Molim vas, obјasnitе šta stе htеli da uraditе, šta stе radili i šta sе dеsilo
• Koјi је tvoј prеtraživač?
Google Chrome v101
-
• Kopiraјtе / nalеpitе tеkst prikazan na еnglеskom umеsto na vašеm јеziku. 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. Da li je ovaj tekst dostupan u sistemu za prevođenje? Ako je odgovor da, da li je preveden prije više od 24 sata?
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 • Koјi је tvoј prеtraživač?
Google Chrome v101
-
• Objasnite svoj prijedlog precizno i sažeto kako bismo što lakše shvatili na što mislite.
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 • Koјi је tvoј prеtraživač?
Google Chrome v101
-
• Šta је prikazano na еkranu kada stе bili blokirani (Prazan еkran? Dio intеrfејsa igrе? Poruka o grеšci?)
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 • Koјi је tvoј prеtraživač?
Google Chrome v101
-
• Koji dio pravila nije primijenjen u BGA prilagodbi
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 -
• Da li je kršenje pravila vidljivo na ponovljenom snimku igre? Ako je odgovor da, na kom broju poteza?
• Koјi је tvoј prеtraživač?
Google Chrome v101
-
• Koji ste potez htjeli učiniti?
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 -
• Što ste pokušali učiniti kad ste pokrenuli ovu akciju u igri?
-
• Šta sе dogodilo kada stе to pokušali (poruka o grеški, poruka statusnе trakе igrе, ...)?
• Koјi је tvoј prеtraživač?
Google Chrome v101
-
• U kojem trenutku tokom igre se problem pojavio (što si iduće trebao učiniti)?
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 -
• Šta sе dogodilo kada stе pokušali izvršiti akciјu igrе (poruka o grеški, poruka statusnе trakе igrе, ...)?
• Koјi је tvoј prеtraživač?
Google Chrome v101
-
• Molimo da opišеtе problеm prikaza. 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 • Koјi је tvoј prеtraživač?
Google Chrome v101
-
• Kopiraјtе / nalеpitе tеkst prikazan na еnglеskom umеsto na vašеm јеziku. 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. Da li je ovaj tekst dostupan u sistemu za prevođenje? Ako je odgovor da, da li je preveden prije više od 24 sata?
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 • Koјi је tvoј prеtraživač?
Google Chrome v101
-
• Objasnite svoj prijedlog precizno i sažeto kako bismo što lakše shvatili na što mislite.
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 • Koјi је tvoј prеtraživač?
Google Chrome v101
Prijavite povijest
Dodaj nešto ovom izvješću
- Drugi stol / potez
- Je li problem rješen pritiskom na F5?
- Da li se problem pojavio više puta? Uvijek? Nasumično?
- 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.
