#149942: "Assign Losses Automatically"

• Falls du eine Fehlermeldung auf dem Bildschirm siehst, bitte kopieren und einfügen.
(Not a bug, just a suggestion.) Currently the game pauses a lot to ask folks to pick which unit will take a loss in battle. But (unless I'm missing something) actually there's no need to do this in most cases because it's usually determined which type of unit has to take the loss, and there's no functional difference between different units in the same category. There are some times where players do have decisions to make, e.g. whether a highland or a non-Highland Metropolitan brigade will take a loss. But there's basically never a reason to take a loss on a Highland rather than another Metropolitan brigade, so even though this is technically a choice I don't think it needs to be on here when it'd slow things down. Which Indian unit to take as a loss sometimes does matter, e.g. in a multi-Year scenario you should preferably take as a loss a unit whose Village is going to be occupied at the start of next Year. So it'd be great to streamline this a bit. Also I'm not sure if the implementation currently always requires you to take losses on an already flipped unit, but 13.4 is clear that Reduced units have loss priority over Full in the same category, so that also removes the need for some decisions.

Thanks so much!
• Bitte erkläre, was du machen wolltest, was du dann getan hast und was dann passiert ist
• Welchen Browser benutzt du?
Google Chrome v131

• Bitte kopiere den Text, der in Englisch anstatt in deiner Sprache angezeigt wird, und füge ihn hier ein. Falls du einen Screenshot dieses Fehlers hast (optimale Vorgehensweise), kannst du ihn bei Imgur.com hochladen, den Link kopieren und hier einfügen.
(Not a bug, just a suggestion.) Currently the game pauses a lot to ask folks to pick which unit will take a loss in battle. But (unless I'm missing something) actually there's no need to do this in most cases because it's usually determined which type of unit has to take the loss, and there's no functional difference between different units in the same category. There are some times where players do have decisions to make, e.g. whether a highland or a non-Highland Metropolitan brigade will take a loss. But there's basically never a reason to take a loss on a Highland rather than another Metropolitan brigade, so even though this is technically a choice I don't think it needs to be on here when it'd slow things down. Which Indian unit to take as a loss sometimes does matter, e.g. in a multi-Year scenario you should preferably take as a loss a unit whose Village is going to be occupied at the start of next Year. So it'd be great to streamline this a bit. Also I'm not sure if the implementation currently always requires you to take losses on an already flipped unit, but 13.4 is clear that Reduced units have loss priority over Full in the same category, so that also removes the need for some decisions.

Thanks so much!
• Ist dieser Text auf der Übersetzungsseite verfügbar? Wenn ja, wurde dieser vor mehr als 24 Stunden übersetzt?
• Welchen Browser benutzt du?
Google Chrome v131

• Bitte erkläre deinen Vorschlag so präzise und genau wie möglich, damit er leicht zu verstehen ist.
(Not a bug, just a suggestion.) Currently the game pauses a lot to ask folks to pick which unit will take a loss in battle. But (unless I'm missing something) actually there's no need to do this in most cases because it's usually determined which type of unit has to take the loss, and there's no functional difference between different units in the same category. There are some times where players do have decisions to make, e.g. whether a highland or a non-Highland Metropolitan brigade will take a loss. But there's basically never a reason to take a loss on a Highland rather than another Metropolitan brigade, so even though this is technically a choice I don't think it needs to be on here when it'd slow things down. Which Indian unit to take as a loss sometimes does matter, e.g. in a multi-Year scenario you should preferably take as a loss a unit whose Village is going to be occupied at the start of next Year. So it'd be great to streamline this a bit. Also I'm not sure if the implementation currently always requires you to take losses on an already flipped unit, but 13.4 is clear that Reduced units have loss priority over Full in the same category, so that also removes the need for some decisions.

Thanks so much!
• Welchen Browser benutzt du?
Google Chrome v131

• Was wurde auf dem Bildschirm angezeigt, als du blockiert wurdest (weißer Bildschirm? Teil der Spieloberfläche? Fehlermeldung?)
(Not a bug, just a suggestion.) Currently the game pauses a lot to ask folks to pick which unit will take a loss in battle. But (unless I'm missing something) actually there's no need to do this in most cases because it's usually determined which type of unit has to take the loss, and there's no functional difference between different units in the same category. There are some times where players do have decisions to make, e.g. whether a highland or a non-Highland Metropolitan brigade will take a loss. But there's basically never a reason to take a loss on a Highland rather than another Metropolitan brigade, so even though this is technically a choice I don't think it needs to be on here when it'd slow things down. Which Indian unit to take as a loss sometimes does matter, e.g. in a multi-Year scenario you should preferably take as a loss a unit whose Village is going to be occupied at the start of next Year. So it'd be great to streamline this a bit. Also I'm not sure if the implementation currently always requires you to take losses on an already flipped unit, but 13.4 is clear that Reduced units have loss priority over Full in the same category, so that also removes the need for some decisions.

Thanks so much!
• Welchen Browser benutzt du?
Google Chrome v131

• Welcher Teil der Spielregel wurde durch die BGA-Adaption nicht beachtet?
(Not a bug, just a suggestion.) Currently the game pauses a lot to ask folks to pick which unit will take a loss in battle. But (unless I'm missing something) actually there's no need to do this in most cases because it's usually determined which type of unit has to take the loss, and there's no functional difference between different units in the same category. There are some times where players do have decisions to make, e.g. whether a highland or a non-Highland Metropolitan brigade will take a loss. But there's basically never a reason to take a loss on a Highland rather than another Metropolitan brigade, so even though this is technically a choice I don't think it needs to be on here when it'd slow things down. Which Indian unit to take as a loss sometimes does matter, e.g. in a multi-Year scenario you should preferably take as a loss a unit whose Village is going to be occupied at the start of next Year. So it'd be great to streamline this a bit. Also I'm not sure if the implementation currently always requires you to take losses on an already flipped unit, but 13.4 is clear that Reduced units have loss priority over Full in the same category, so that also removes the need for some decisions.

Thanks so much!
• Ist der Regelverstoß in der Spielwiederholung zu sehen? Falls ja, bei welcher Zugnummer?
• Welchen Browser benutzt du?
Google Chrome v131

• Welche Spielaktion wolltest du durchführen?
(Not a bug, just a suggestion.) Currently the game pauses a lot to ask folks to pick which unit will take a loss in battle. But (unless I'm missing something) actually there's no need to do this in most cases because it's usually determined which type of unit has to take the loss, and there's no functional difference between different units in the same category. There are some times where players do have decisions to make, e.g. whether a highland or a non-Highland Metropolitan brigade will take a loss. But there's basically never a reason to take a loss on a Highland rather than another Metropolitan brigade, so even though this is technically a choice I don't think it needs to be on here when it'd slow things down. Which Indian unit to take as a loss sometimes does matter, e.g. in a multi-Year scenario you should preferably take as a loss a unit whose Village is going to be occupied at the start of next Year. So it'd be great to streamline this a bit. Also I'm not sure if the implementation currently always requires you to take losses on an already flipped unit, but 13.4 is clear that Reduced units have loss priority over Full in the same category, so that also removes the need for some decisions.

Thanks so much!
• Was versuchst du, um diese Spielaktion auszulösen?
• Was passiert, wenn du dies versuchst (Fehlermeldung, Statusmeldung des Spiels, ...)?
• Welchen Browser benutzt du?
Google Chrome v131

• An welcher Stelle im Spiel ist das Problem aufgetreten? Was war die aktuelle Spielanweisung?
(Not a bug, just a suggestion.) Currently the game pauses a lot to ask folks to pick which unit will take a loss in battle. But (unless I'm missing something) actually there's no need to do this in most cases because it's usually determined which type of unit has to take the loss, and there's no functional difference between different units in the same category. There are some times where players do have decisions to make, e.g. whether a highland or a non-Highland Metropolitan brigade will take a loss. But there's basically never a reason to take a loss on a Highland rather than another Metropolitan brigade, so even though this is technically a choice I don't think it needs to be on here when it'd slow things down. Which Indian unit to take as a loss sometimes does matter, e.g. in a multi-Year scenario you should preferably take as a loss a unit whose Village is going to be occupied at the start of next Year. So it'd be great to streamline this a bit. Also I'm not sure if the implementation currently always requires you to take losses on an already flipped unit, but 13.4 is clear that Reduced units have loss priority over Full in the same category, so that also removes the need for some decisions.

Thanks so much!
• Was passiert, wenn du die Spielaktion ausführen möchtest (Fehlermeldung, Statusmeldung des Spiels, ...)?
• Welchen Browser benutzt du?
Google Chrome v131

• Bitte beschreibe die Anzeigeschwierigkeiten. Falls du einen Screenshot dieses Fehlers hast (optimale Vorgehensweise), kannst du ihn bei Imgur.com hochladen, den Link kopieren und hier einfügen.
(Not a bug, just a suggestion.) Currently the game pauses a lot to ask folks to pick which unit will take a loss in battle. But (unless I'm missing something) actually there's no need to do this in most cases because it's usually determined which type of unit has to take the loss, and there's no functional difference between different units in the same category. There are some times where players do have decisions to make, e.g. whether a highland or a non-Highland Metropolitan brigade will take a loss. But there's basically never a reason to take a loss on a Highland rather than another Metropolitan brigade, so even though this is technically a choice I don't think it needs to be on here when it'd slow things down. Which Indian unit to take as a loss sometimes does matter, e.g. in a multi-Year scenario you should preferably take as a loss a unit whose Village is going to be occupied at the start of next Year. So it'd be great to streamline this a bit. Also I'm not sure if the implementation currently always requires you to take losses on an already flipped unit, but 13.4 is clear that Reduced units have loss priority over Full in the same category, so that also removes the need for some decisions.

Thanks so much!
• Welchen Browser benutzt du?
Google Chrome v131

• Bitte kopiere den Text, der in Englisch anstatt in deiner Sprache angezeigt wird, und füge ihn hier ein. Falls du einen Screenshot dieses Fehlers hast (optimale Vorgehensweise), kannst du ihn bei Imgur.com hochladen, den Link kopieren und hier einfügen.
(Not a bug, just a suggestion.) Currently the game pauses a lot to ask folks to pick which unit will take a loss in battle. But (unless I'm missing something) actually there's no need to do this in most cases because it's usually determined which type of unit has to take the loss, and there's no functional difference between different units in the same category. There are some times where players do have decisions to make, e.g. whether a highland or a non-Highland Metropolitan brigade will take a loss. But there's basically never a reason to take a loss on a Highland rather than another Metropolitan brigade, so even though this is technically a choice I don't think it needs to be on here when it'd slow things down. Which Indian unit to take as a loss sometimes does matter, e.g. in a multi-Year scenario you should preferably take as a loss a unit whose Village is going to be occupied at the start of next Year. So it'd be great to streamline this a bit. Also I'm not sure if the implementation currently always requires you to take losses on an already flipped unit, but 13.4 is clear that Reduced units have loss priority over Full in the same category, so that also removes the need for some decisions.

Thanks so much!
• Ist dieser Text auf der Übersetzungsseite verfügbar? Wenn ja, wurde dieser vor mehr als 24 Stunden übersetzt?
• Welchen Browser benutzt du?
Google Chrome v131

• Bitte erkläre deinen Vorschlag so präzise und genau wie möglich, damit er leicht zu verstehen ist.
(Not a bug, just a suggestion.) Currently the game pauses a lot to ask folks to pick which unit will take a loss in battle. But (unless I'm missing something) actually there's no need to do this in most cases because it's usually determined which type of unit has to take the loss, and there's no functional difference between different units in the same category. There are some times where players do have decisions to make, e.g. whether a highland or a non-Highland Metropolitan brigade will take a loss. But there's basically never a reason to take a loss on a Highland rather than another Metropolitan brigade, so even though this is technically a choice I don't think it needs to be on here when it'd slow things down. Which Indian unit to take as a loss sometimes does matter, e.g. in a multi-Year scenario you should preferably take as a loss a unit whose Village is going to be occupied at the start of next Year. So it'd be great to streamline this a bit. Also I'm not sure if the implementation currently always requires you to take losses on an already flipped unit, but 13.4 is clear that Reduced units have loss priority over Full in the same category, so that also removes the need for some decisions.

Thanks so much!
• Welchen Browser benutzt du?
Google Chrome v131

Worum geht es bei dieser Meldung?

Was ist passiert? Bitte wähle unten aus

Was ist passiert? Bitte wähle unten aus

Bitte überprüfe, ob bereits eine Meldung zum gleichen Thema existiert

Detaillierte Beschreibung

Meldungshistorie

Ergänze diese Meldung

Ändere den Status der Meldung auf:

Hilfe

Leiste einen Beitrag

Folge uns