#64967: "Provide SOME warning that you are going to collide before finishing the movement phase"
Mitä tämä raportti koskee?
Mitä tapahtui? Valitse alta
Mitä tapahtui? Valitse alta
Ennen ilmoituksen tekoa, tarkista onko sellainen jo olemassa samasta aiheesta
Jos kyllä, ole ystävällinen ja ÄÄNESTÄ tätä raporttia. Eniten ääniä saaneet raportit laitetaan ETUSIJALLE!
# | Status | Votes | Game | Type | Title | Last update |
---|
Tarkka kuvaus
-
• Kopioi/liitä virheilmoitus näytöltäsi, jos sait sellaisen.
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 -
• Selitä mitä halusit tehdä, mitä teit ja mitä tapahtui
• Mikä on selaimesi?
Google Chrome v101
-
• Ole hyvä ja kopioi teksti englanniksi oman kielesi sijasta. Jos sinulla on kuvankaappaus tästä bugista, voit käyttää Imgur.com:a sen lähettämiseksi. Kopioi ja liitä linkki tähän.
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 -
• Onko tämä teksti saatavilla käännösjärjestelmässä? Jos on, onko sen käännöksestä yli 24 tuntia?
• Mikä on selaimesi?
Google Chrome v101
-
• Selitä ehdotuksesti tarkasti ja ytimekkäästi, jotta se on ymmärrettävissä niin helposti kuin mahdollista.
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 • Mikä on selaimesi?
Google Chrome v101
-
• Mitä näytöllä näkyi kun olit estettynä (Tyhjä ruutu? Osa pelin käyttöliittymästä? Virheilmoitus?)
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 • Mikä on selaimesi?
Google Chrome v101
-
• Mitä osaa säännöistä BGA:n sovellus ei noudattanut
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 -
• Onko sääntörikkomus nähtävillä pelin toistossa? Jos kyllä, mikä on siirron numero?
• Mikä on selaimesi?
Google Chrome v101
-
• Minkä pelin toiminnon halusit suorittaa?
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 -
• Mitä yritit tehdä tämän pelitoiminnon käynnistymiseksi?
-
• Mitä tapahtui kun yritit tehdä tämän (virheilmoitus, pelin tilapalkin viesti, ...)?
• Mikä on selaimesi?
Google Chrome v101
-
• Missä vaiheessa peliä ongelma ilmeni (mikä oli silloinen pelin ohje)?
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 -
• Mitä tapahtui kun yritit tehdä tämän pelin toiminnon (virheilmoitus, pelin tilapalkin viesti, ...)?
• Mikä on selaimesi?
Google Chrome v101
-
• Kuvaile näyttöongelmaa. Jos sinulla on kuvankaappaus tästä bugista, voit käyttää Imgur.com:a sen lähettämiseksi. Kopioi ja liitä linkki tähän.
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 • Mikä on selaimesi?
Google Chrome v101
-
• Ole hyvä ja kopioi teksti englanniksi oman kielesi sijasta. Jos sinulla on kuvankaappaus tästä bugista, voit käyttää Imgur.com:a sen lähettämiseksi. Kopioi ja liitä linkki tähän.
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 -
• Onko tämä teksti saatavilla käännösjärjestelmässä? Jos on, onko sen käännöksestä yli 24 tuntia?
• Mikä on selaimesi?
Google Chrome v101
-
• Selitä ehdotuksesti tarkasti ja ytimekkäästi, jotta se on ymmärrettävissä niin helposti kuin mahdollista.
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 • Mikä on selaimesi?
Google Chrome v101
Raportin historia
Lisää jotain tähän raporttiin
- Toinen pöydän tunnus / siirron numero
- Ratkaisiko F5 ongelman?
- Ilmestyykö ongelma useita kertoja? Joka kerta? Satunnaisesti?
- Jos sinulla on kuvankaappaus tästä bugista, voit käyttää Imgur.com:a sen lähettämiseksi. Kopioi ja liitä linkki tähän.