• Kopieer en plak alsjeblieft de foutboodschap die je op je scherm ziet, indien van toepassing.

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

• Leg uit wat je wilde doen, wat je deed en wat er gebeurde

• Welke browser gebruik je?

• Kopieer en plak alsjeblieft de tekst die in het Engels wordt getoond in plaats van in jouw taal. Als je een schermkopie van deze bug hebt (goede gewoonte), kun je een hosting-service voor afbeeldingen naar keuze gebruiken (bijvoorbeeld snipboard.io) om deze te uploaden en de link hier te kopiëren/plakken. Is deze tekst beschikbaar in het vertaalsysteem? Zo ja, is deze meer dan 24 uur geleden vertaald?

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

• Welke browser gebruik je?

• Gelieve jouw suggestie precies en beknopt uit te leggen zodat het zo makkelijk mogelijk is om te begrijpen wat je bedoelt.

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

• Welke browser gebruik je?

• Wat stond op het scherm toen je geblokkeerd was (Leeg scherm? Een deel van de spelinterface? Foutboodschap?)

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

• Welke browser gebruik je?

• Met welk onderdeel van de regels is geen rekening gehouden bij de BGA-versie?

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

• Is de inbreuk op de spelregels zichtbaar in de spelherhaling? Indien ja, bij welk zetnummer?

• Welke browser gebruik je?

• Welke spelactie wilde je uitvoeren?

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

• Wat probeerde je te doen om deze spelactie te laten optreden?

• Wat gebeurde er toen je dit probeerde te doen (foutboodschap, melding op de statusbalk van het spel, ...)?

• Welke browser gebruik je?

• In welke fase van het spel deed het probleem zich voor (wat was de huidige spelinstructie)?

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

• Wat gebeurde toen je deze spelactie probeerde (foutboodschap, melding op de statusbalk van het spel, ...)?

• Welke browser gebruik je?

• Beschrijf alsjeblieft het probleem met de beeldweergave. Als je een schermkopie van deze bug hebt (goede gewoonte), kun je een hosting-service voor afbeeldingen naar keuze gebruiken (bijvoorbeeld snipboard.io) om deze te uploaden en de link hier te kopiëren/plakken.

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

• Welke browser gebruik je?

• Kopieer en plak alsjeblieft de tekst die in het Engels wordt getoond in plaats van in jouw taal. Als je een schermkopie van deze bug hebt (goede gewoonte), kun je een hosting-service voor afbeeldingen naar keuze gebruiken (bijvoorbeeld snipboard.io) om deze te uploaden en de link hier te kopiëren/plakken. Is deze tekst beschikbaar in het vertaalsysteem? Zo ja, is deze meer dan 24 uur geleden vertaald?

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

• Welke browser gebruik je?

• Gelieve jouw suggestie precies en beknopt uit te leggen zodat het zo makkelijk mogelijk is om te begrijpen wat je bedoelt.

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

• Welke browser gebruik je?