#149942: "Assign Losses Automatically"
Kāds ir šis ziņojums?
Kas notika? Lūdzu izvēlies no zemākredzamajiem
Kas notika? Lūdzu izvēlies no zemākredzamajiem
Lūdzu, pārbaudiet, vai par šo pašu tēmu jau ir ziņojums
Ja jā, lūdzu, balsojiet par šo ziņojumu. Ziņojumiem ar vislielākajām balsīm tiek dota PRIORITĀTE!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detalizēts apraksts
-
• Lūdzu nokopē/ielīmē kļūdas ziņu, ko redzi ekrānā, ja tāda ir.
(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! -
• Lūdzu paskaidro, ko Tu vēlējies darīt, ko Tu izdarīji un kas notika
• Kāda ir Tava pārlūkprogramma?
Google Chrome v131
-
• Lūdzu iekopē tekstu, kas redzams angļu, nevis tavā valodā. Ja Tev ir ekrānuzņēmums, kurā redzama kļūme (laba prakse), vari izmantot Imgur.com , lai to augšupielādētu un kopētu/ielīmētu saiti šeit.
(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! -
• Vai šis teksts ir pieejams tulkošanas sistēmā? Ja jā, vai tas ir ticis tulkots pēdējo 24 stundu laikā?
• Kāda ir Tava pārlūkprogramma?
Google Chrome v131
-
• Lūdzu, paskaidrojiet savu ieteikumu precīzi un kodolīgi, lai tas būtu pēc iespējas vieglāk saprotams.
(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! • Kāda ir Tava pārlūkprogramma?
Google Chrome v131
-
• Kas tika attēlots ekrānā, kad Tu tiki bloķēts (tukšs ekrāns? Daļa no spēles interfeisa? Ziņa par kļūdu?)?
(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! • Kāda ir Tava pārlūkprogramma?
Google Chrome v131
-
• Kura noteikumu daļa netika ņemta vērā BGA versijā?
(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! -
• Vai noteikumu pārkāpums ir redzams spēles atkārtojumā? Ja jā, tad kurā gājienā?
• Kāda ir Tava pārlūkprogramma?
Google Chrome v131
-
• Kādu spēles darbību Tu vēlējies veikt?
(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! -
• Ko tu dari, lai panāktu šo spēles darbību?
-
• Kas notika, kad veicāt šo darbību (kļūdas paziņojums, spēles informācijas paziņojums,...)?
• Kāda ir Tava pārlūkprogramma?
Google Chrome v131
-
• Kurā spēles solī problēma parādījās (kas bija tā brīža spēles instrukcija)?
(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! -
• Kas notika, kad mēģinājāt veikt spēles darbību (kļūdas paziņojums, spēles informācijas paziņojums,...)?
• Kāda ir Tava pārlūkprogramma?
Google Chrome v131
-
• Lūdzu aprakstiet radušos problēmu. Ja Tev ir ekrānuzņēmums, kurā redzama kļūme (laba prakse), vari izmantot Imgur.com , lai to augšupielādētu un kopētu/ielīmētu saiti šeit.
(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! • Kāda ir Tava pārlūkprogramma?
Google Chrome v131
-
• Lūdzu iekopē tekstu, kas redzams angļu, nevis tavā valodā. Ja Tev ir ekrānuzņēmums, kurā redzama kļūme (laba prakse), vari izmantot Imgur.com , lai to augšupielādētu un kopētu/ielīmētu saiti šeit.
(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! -
• Vai šis teksts ir pieejams tulkošanas sistēmā? Ja jā, vai tas ir ticis tulkots pēdējo 24 stundu laikā?
• Kāda ir Tava pārlūkprogramma?
Google Chrome v131
-
• Lūdzu, paskaidrojiet savu ieteikumu precīzi un kodolīgi, lai tas būtu pēc iespējas vieglāk saprotams.
(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! • Kāda ir Tava pārlūkprogramma?
Google Chrome v131
Ziņojuma vēsture
Note that it's already assigning hits to reduced units automatically or if there is only one option for a given unit type.
Pievieno kaut ko šim ziņojumam
- Cita galda ID / gājiena ID
- Vai F5 atrisināja šo problēmu?
- Vai šī problēma parādās vairākas reizes? Katru reizi? Nekonkrētās reizēs?
- Ja Tev ir ekrānuzņēmums, kurā redzama kļūme (laba prakse), vari izmantot Imgur.com , lai to augšupielādētu un kopētu/ielīmētu saiti šeit.
