#149942: "Assign Losses Automatically"
O czym jest to zgłoszenie?
Co się stało? Wybierz z poniższych opcji
Co się stało? Wybierz z poniższych opcji
Sprawdź, czy istnieje już zgłoszenie na ten sam temat
Jeśli tak, ZAGŁOSUJ na to zgłoszenie. Zgłoszenia z największą liczbą głosów mają najwyższy PRIORYTET!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Szczegółowy opis
-
• Proszę skopiować i wkleić treść błędu wyświetloną na ekranie, o ile jakaś się pojawia.
(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! -
• Proszę opisać co chciałeś zrobić, co zrobiłeś i co się stało
• Jaką masz przeglądarkę?
Google Chrome v131
-
• Proszę skopiować i wkleić tekst wyświetlany w języku angielskim zamiast w twoim języku. Jeżeli masz zrzut ekranu z tym błędem (dobry zwyczaj) możesz użyć Imgur.com, żeby wrzucić go do Internetu i potem skopiować łącze do niego tutaj.
(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! -
• Czy ten tekst jest dostępny w systemie tłumaczeń? Jeśli tak, to czy został przetłumaczony więcej niż 24 godziny temu?
• Jaką masz przeglądarkę?
Google Chrome v131
-
• Wyjaśnij swoją propozycję precyzyjnie i zwięźle, tak aby jak najłatwiej zrozumieć, co masz na myśli.
(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! • Jaką masz przeglądarkę?
Google Chrome v131
-
• Co wyświetlało się na ekranie kiedy zostałeś zablokowany (Pusty ekran? Część interfejsu gry? Komunikat o błędzie?)
(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! • Jaką masz przeglądarkę?
Google Chrome v131
-
• Która z zasad gry nie była przestrzegana w adaptacji 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! -
• Czy naruszenie zasad gry jest widoczne w powtórce rozgrywki? Jeżeli tak, to w ruchu o jakim numerze?
• Jaką masz przeglądarkę?
Google Chrome v131
-
• Jaką akcję w grze chciałeś wykonać?
(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! -
• Co starasz się zrobić by uruchomić tę akcję w grze?
-
• Co się stało kiedy próbowałeś to zrobić (komunikat o błędzie, komunikat na pasku stanu gry, ...)?
• Jaką masz przeglądarkę?
Google Chrome v131
-
• W którym momencie gry pojawił się problem (jakie było aktualne polecenie w grze)?
(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! -
• Co się stało kiedy próbowałeś wykonać akcję w grze (komunikat o błędzie, komunikat na pasku stanu gry, ...)?
• Jaką masz przeglądarkę?
Google Chrome v131
-
• Proszę opisać problem z wyświetlaniem. Jeżeli masz zrzut ekranu z tym błędem (dobry zwyczaj) możesz użyć Imgur.com, żeby wrzucić go do Internetu i potem skopiować łącze do niego tutaj.
(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! • Jaką masz przeglądarkę?
Google Chrome v131
-
• Proszę skopiować i wkleić tekst wyświetlany w języku angielskim zamiast w twoim języku. Jeżeli masz zrzut ekranu z tym błędem (dobry zwyczaj) możesz użyć Imgur.com, żeby wrzucić go do Internetu i potem skopiować łącze do niego tutaj.
(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! -
• Czy ten tekst jest dostępny w systemie tłumaczeń? Jeśli tak, to czy został przetłumaczony więcej niż 24 godziny temu?
• Jaką masz przeglądarkę?
Google Chrome v131
-
• Wyjaśnij swoją propozycję precyzyjnie i zwięźle, tak aby jak najłatwiej zrozumieć, co masz na myśli.
(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! • Jaką masz przeglądarkę?
Google Chrome v131
Historia zgłoszeń
Note that it's already assigning hits to reduced units automatically or if there is only one option for a given unit type.
Dodaj coś do tego zgłoszenia
- Kolejne ID stołu / ID ruchu
- Czy F5 rozwiązało problem?
- Czy problem zdarzył się kilka razy? Za każdym razem? Losowo?
- Jeżeli masz zrzut ekranu z tym błędem (dobry zwyczaj) możesz użyć Imgur.com, żeby wrzucić go do Internetu i potem skopiować łącze do niego tutaj.
