#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

รายงานนี้เกี่ยวกับอะไร?

เกิดอะไรขึ้น? กรุณาเลือกจากด้านล่าง

เกิดอะไรขึ้น? กรุณาเลือกจากด้านล่าง

โปรดตรวจสอบว่ามีรายงานในหัวข้อเดียวกันอยู่แล้ว

คำอธิบายโดยละเอียด

ประวัติการรายงาน

เพิ่มการร้องเรียน

เปลี่ยนสถานะรายงานเป็น:

ช่วยเหลือ

สนับสนุน

ติดตามเรา