#149942: "Assign Losses Automatically"

• 만약 오류 메세지가 화면에 나타났다면, 그 오류 메세지를 복사해서 붙여넣어 주시기 바랍니다.
(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!
• 무엇을 하고 싶었고, 무엇을 했고, 무슨 일이 일어났는지를 설명해 주십시오
• 브라우저가 무엇입니까?
Google Chrome v131

• 현재 설정된 언어가 아니라 영어로 표시되는 문장을 복사 후 붙여넣어 주세요. 만약에 버그에 대한 스크린샷을 가지고 계신다면 Imgur.com 사이트에 업로드 하시고, 여기에 링크를 복사/붙여넣기 하시기 바랍니다.
(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!
• 해당 문장이 번역 본부에서 표시됩니까? 만약 그렇다면, 번역된 지 24시간이 경과했습니까?
• 브라우저가 무엇입니까?
Google Chrome v131

• 최대한 쉽게 그 뜻을 이해할 수 있도록 당신의 제안을 정확하고 명료하게 설명해 주십시오.
(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!
• 브라우저가 무엇입니까?
Google Chrome v131

• 당신이 막혔을 때 화면에 무엇이 나타났습니까?(검은 화면? 게임 인터페이스? 오류 메시지?)
(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!
• 브라우저가 무엇입니까?
Google Chrome v131

• 어느 규칙이 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!
• 게임 리플레이에서 룰 위반을 확인할 수 있습니까?만약 그렇다면, 몇번째 수에서 룰 위반이 있나요?
• 브라우저가 무엇입니까?
Google Chrome v131

• 당신이 하고 싶었던 게임 내 행동이 어느 것입니까?
(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!
• 이 게임 행동을 하기 위해 무엇을 시도했습니까?
• 당신이 이것을 하려고 했을 때 무슨 일이 일어났습니까?(오류 메시지, 게임 상태창 메시지 등)
• 브라우저가 무엇입니까?
Google Chrome v131

• 어떤 부분에서 문제가 발생 하였나요(문제가 발생했을 당시 어떤 지시가 내려졌었나요)?
(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!
• 당신이 게임 행동을 하려 했을 때 무슨 일이 일어났습니까?(오류 메시지, 게임 상태 막대 메시지, ...)
• 브라우저가 무엇입니까?
Google Chrome v131

• 디스플레이 문제를 설명해주세요. 만약에 버그에 대한 스크린샷을 가지고 계신다면 Imgur.com 사이트에 업로드 하시고, 여기에 링크를 복사/붙여넣기 하시기 바랍니다.
(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!
• 브라우저가 무엇입니까?
Google Chrome v131

• 현재 설정된 언어가 아니라 영어로 표시되는 문장을 복사 후 붙여넣어 주세요. 만약에 버그에 대한 스크린샷을 가지고 계신다면 Imgur.com 사이트에 업로드 하시고, 여기에 링크를 복사/붙여넣기 하시기 바랍니다.
(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!
• 해당 문장이 번역 본부에서 표시됩니까? 만약 그렇다면, 번역된 지 24시간이 경과했습니까?
• 브라우저가 무엇입니까?
Google Chrome v131

• 최대한 쉽게 그 뜻을 이해할 수 있도록 당신의 제안을 정확하고 명료하게 설명해 주십시오.
(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!
• 브라우저가 무엇입니까?
Google Chrome v131

무엇에 대한 보고입니까?

무슨 일이 발생했나요? 아래에서 선택하세요

무슨 일이 발생했나요? 아래에서 선택하세요

같은 내용에 대하여 이미 등록된 보고가 있는지 확인해주세요

상세한 설명

보고 이력

리포트에 내용 추가하기

보고의 상태를 다음으로 변경:

도움말

기여하기

저희를 팔로우해주세요