#64967: "Provide SOME warning that you are going to collide before finishing the movement phase"
В какво се състои този доклад?
Какво се случи? Моля изберете от списъка по-долу
Какво се случи? Моля изберете от списъка по-долу
Моля, проверете дали вече има доклад по същия въпрос
Ако отговорът е „да“, моля, гласувайте за този доклад. Отчетите с най-много гласове са дадени ПРИОРИТЕТ!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Подробно описание
-
• Моля поставете тук съобщението за грешка което виждате, ако има такова
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 -
• Моля обяснете, какво искахте да направите, какво направихте и какво се случи
• Какъв е вашия браузър?
Google Chrome v101
-
• Моля копирайте/поставете текстът показан на аглийски, вместо на Вашия език. 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. Наличен ли е този текст в системата за превод? Ако да, бил ли е преведен за повече от 24 часа?
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 • Какъв е вашия браузър?
Google Chrome v101
-
• Моля обяснете вашето придложение ясно и кратко така че да бъде възможно най-разбираемо.
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 • Какъв е вашия браузър?
Google Chrome v101
-
• Какво е било показано на екрана, когато сте били блокирани (празен екран? Част от интерфейса на играта? Съобщение за грешка?)
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 • Какъв е вашия браузър?
Google Chrome v101
-
• Коя част от правилата не е била спазена от BGA адаптацията
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 -
• Нарушенията на правилата видими ли са при повторение на играта? Ако да, на кой ход се случват?
• Какъв е вашия браузър?
Google Chrome v101
-
• Какъв бе игровият ход, който се опитахте да извършите?
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 -
• Какво се опитвате да направите, за да задействате тази игра?
-
• Какво се случи, когато се опитахте да направите това (съобщение за грешка, съобщение за статуса на играта, ...)?
• Какъв е вашия браузър?
Google Chrome v101
-
• В кой момент от играта се появи проблема (каква е била съответната инструкция в играта)?
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 -
• Какво се случи, когато се опитахте да извършите действието в играта (съобщение за грешка, съобщение за статуса на играта, ...)?
• Какъв е вашия браузър?
Google Chrome v101
-
• Моля опишете грешката при изобразяването 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 • Какъв е вашия браузър?
Google Chrome v101
-
• Моля копирайте/поставете текстът показан на аглийски, вместо на Вашия език. 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. Наличен ли е този текст в системата за превод? Ако да, бил ли е преведен за повече от 24 часа?
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 • Какъв е вашия браузър?
Google Chrome v101
-
• Моля обяснете вашето придложение ясно и кратко така че да бъде възможно най-разбираемо.
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 • Какъв е вашия браузър?
Google Chrome v101
История на докладванията
Добави нещо към този доклад
- Друга маса ID / Ход ID
- F5 реши ли проблема?
- Проблемът няколко пъти ли се е появил? Или всеки път? Или абсолютно случайно?
- 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.
