• Kopirajte / prilepite sporočilo o napaki, ki ga vidite na zaslonu, če ga imate.

(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!

• Prosim, pojasnite, kaj ste hoteli storiti, kaj ste naredili in kaj se je zgodilo

• Kateri brskalnik uporabljaš?

• Kopirajte / prilepite besedilo, prikazano v angleščini, namesto v vašem jeziku. Če imate sliko zaslona te napake (dobra praksa), lahko uporabite Imgur.com za nalaganje in kopirate/prilepite povezavo do slike tukaj.

(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 ta tekst dosegljiv v prevajalnem sistemu? Če ja, ali je bil preveden več kot 24 ur nazaj?

• Kateri brskalnik uporabljaš?

• Natančno in jedrnato pojasnite svoj predlog, da bo čim lažje razumeti, kaj mislite.

(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!

• Kateri brskalnik uporabljaš?

• Kaj je bilo prikazano na zaslonu, ko ste bili blokirani (prazen zaslon? Del vmesnika za igro? Sporočilo o napaki?)

(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!

• Kateri brskalnik uporabljaš?

• Kateri del pravil ni bil upoštevan pri priredbi za 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 kršitev pravil vidna na seznamu potez? Če je, pri kateri številki poteze?

• Kateri brskalnik uporabljaš?

• Katero potezo ste želeli narediti v igri?

(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!

• Kaj ste poskušali narediti, da bi izvedli to potezo v igri?

• Kaj se je zgodilo, ko ste poskusili to storiti (sporočilo o napaki, sporočilo v vrstici stanja, ...)?

• Kateri brskalnik uporabljaš?

• Na kateri točki v igri se je težava pojavila (katera navodila so bila prikazana)

(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!

• Kaj se je zgodilo, ko ste poskušali narediti to potezo v igri (sporočilo o napaki, sporočilo v vrstici stanja, ...)?

• Kateri brskalnik uporabljaš?

• Prosim opiši problem s prikazom. Če imate sliko zaslona te napake (dobra praksa), lahko uporabite Imgur.com za nalaganje in kopirate/prilepite povezavo do slike tukaj.

(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!

• Kateri brskalnik uporabljaš?

• Kopirajte / prilepite besedilo, prikazano v angleščini, namesto v vašem jeziku. Če imate sliko zaslona te napake (dobra praksa), lahko uporabite Imgur.com za nalaganje in kopirate/prilepite povezavo do slike tukaj.

(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 ta tekst dosegljiv v prevajalnem sistemu? Če ja, ali je bil preveden več kot 24 ur nazaj?

• Kateri brskalnik uporabljaš?

• Natančno in jedrnato pojasnite svoj predlog, da bo čim lažje razumeti, kaj mislite.

(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!

• Kateri brskalnik uporabljaš?