• Please copy/paste the error message you see on your screen, if applicable.

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

• Please explain what you wanted to do, what you did and what happened

• Which browser are you using?

• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.

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

• Is this text available in the translation system? If yes, has it been translated for more than 24 hours?

• Which browser are you using?

• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.

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

• Which browser are you using?

• What was displayed on the screen when you were blocked (Blank screen? Part of the game interface? Error message?)

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

• Which browser are you using?

• Which part of the rules was not followed by the BGA adaptation?

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

• Is the rules violation visible on game replay? If yes, at which move number?

• Which browser are you using?

• What was the game action you wanted to do?

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

• What did you try to do to trigger this game action?

• What happened when you tried to do this (error message, game status bar message, ...)?

• Which browser are you using?

• At which step of the game did the problem occur? What was the current game instruction?

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

• What happened when you tried to do this game action (error message, game status bar message, ...)?

• Which browser are you using?

• Please describe the display issue. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.

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

• Which browser are you using?

• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.

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

• Is this text available in the translation system? If yes, has it been translated for more than 24 hours?

• Which browser are you using?

• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.

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

• Which browser are you using?