#149942: "Assign Losses Automatically"
Čeho se toto hlášení týká?
Co se stalo? Prosím vyberte níže
Co se stalo? Prosím vyberte níže
Prosím zkontroluj, zda již neexistuje hlášení pro stejnou věc
Pokud ano, HLASUJ pro toto hlášení. Hlášení s nejvyšším počtem hlasů budou řešena PŘEDNOSTNĚ!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detailní popis
-
• Prosím, zkopíruj a vlož hlášení o chybě, které vidíš na monitoru, pokud to lze.
(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! -
• Prosím popiš, co jsi měl v úmyslu udělat, co jsi udělal a co se nakonec stalo
• Jaký prohlížeč používáte?
Google Chrome v131
-
• Prosíme, zkopíruj/vlož text zobrazený v angličtině namísto tvého jazyka. Pokud máš snímek obrazvky zobrazující tuto chybu (doporučujeme!), můžeš použít Imgur.com pro nahrání obrázku a pak odkaz na tento obrázek na Imguru zkopírovat a vložit sem.
(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! -
• Je tento text k dispozici v systému pro překládání? Pokud ano, byl přeložen před více než 24 hodinami?
• Jaký prohlížeč používáte?
Google Chrome v131
-
• Prosím popiš svůj návrh přesně a konzistentně, aby bylo snadné pochopit, co máš na mysli.
(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! • Jaký prohlížeč používáte?
Google Chrome v131
-
• Co bylo zobrazeno na monitoru, když došlo k tvému zablokování? (Černá obrazovka? Část herního prostředí? Hlášení o chybě?)
(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! • Jaký prohlížeč používáte?
Google Chrome v131
-
• Která část pravidel nebyla dodržena adaptací hry na BGA
(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! -
• Je vidět porušení pravidel na záznamu hry? Pokud ano, ve kterém tahu?
• Jaký prohlížeč používáte?
Google Chrome v131
-
• O jakou herní akci ses pokoušel/a?
(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! -
• Co ses pokoušel/a udělat, abys spustil/a tuhle herní akci?
-
• Co se stalo, když ses o tuto akci pokusil/a (vyskočila chybová hláška, lišta ve hře, ...)?
• Jaký prohlížeč používáte?
Google Chrome v131
-
• V jaké fázi hry problém nastal (jaký byl poslední herní pokyn)?
(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! -
• Co se stalo, když ses pokusil/a udělat akci (chybová hláška, oznámení stavového řádku hry, ...)?
• Jaký prohlížeč používáte?
Google Chrome v131
-
• Prosím popište vyobrazený problém. Pokud máš snímek obrazvky zobrazující tuto chybu (doporučujeme!), můžeš použít Imgur.com pro nahrání obrázku a pak odkaz na tento obrázek na Imguru zkopírovat a vložit sem.
(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! • Jaký prohlížeč používáte?
Google Chrome v131
-
• Prosíme, zkopíruj/vlož text zobrazený v angličtině namísto tvého jazyka. Pokud máš snímek obrazvky zobrazující tuto chybu (doporučujeme!), můžeš použít Imgur.com pro nahrání obrázku a pak odkaz na tento obrázek na Imguru zkopírovat a vložit sem.
(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! -
• Je tento text k dispozici v systému pro překládání? Pokud ano, byl přeložen před více než 24 hodinami?
• Jaký prohlížeč používáte?
Google Chrome v131
-
• Prosím popiš svůj návrh přesně a konzistentně, aby bylo snadné pochopit, co máš na mysli.
(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! • Jaký prohlížeč používáte?
Google Chrome v131
Historie hlášení
Note that it's already assigning hits to reduced units automatically or if there is only one option for a given unit type.
Doplňte tuto zprávu
- ID dalšího stolu / ID tahu
- Byla chyba odstraněna stisknutím F5?
- Objevila se tato chyba častěji? Pokaždé? Náhodně?
- Pokud máš snímek obrazvky zobrazující tuto chybu (doporučujeme!), můžeš použít Imgur.com pro nahrání obrázku a pak odkaz na tento obrázek na Imguru zkopírovat a vložit sem.
