• Παρακαλούμε κάντε αντιγραφή/επικόλληση του μηνύματος που βλέπετε στην οθόνη σας, αν υπάρχει.

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

• Παρακαλώ εξηγήστε τι θέλατε να κάνατε, τι κάνατε και τι συνέβη

• Ποιο είναι το πρόγραμμα περιήγησής σου;

• Παρακαλώ κάνε αντιγραφή/επικόλληση του κειμένου που απεικονίζεται στα αγγλικά αντί για αυτό που είναι στη γλώσσα σου.. Αν έχεις απόσπασμα οθόνης από αυτό το σφάλμα (είναι καλή αυτή η πρακτική), μπορείς να χρησιμοποιήσεις το 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 ώρες;

• Ποιο είναι το πρόγραμμα περιήγησής σου;

• Παρακάλώ εξηγήστε την πρότασή σας με ακρίβεια και περιεκτικότητα, ώστε να είναι όσο το δυνατόν πιο εύκολο να γίνει αντιληπτό τι εννοείτε.

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

• Ποιο είναι το πρόγραμμα περιήγησής σου;

• Τι εμφανιζόταν στην οθόνη όταν σταμάτησε (Κενή οθόνη; Μέρος του περιβάλλοντος του παιχνιδιού; Μήνυμα σφάλματος;)

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

• Ποιο είναι το πρόγραμμα περιήγησής σου;

• Ποιο μέρος των κανόνων δεν έγινε σεβαστό από την μετατροπή του παιχνιδιού για την 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!

• Είναι η παραβίαση των κανόνων ορατή στην αναπαραγωγή του παιχνιδιού; Αν ναι, σε ποια κίνηση;

• Ποιο είναι το πρόγραμμα περιήγησής σου;

• Ποια ήταν η δράση του παιχνιδιού που ήθελες να κάνεις;

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

• Τι προσπαθείτε να κάνετε για να ενεργοποιείσετε αυτήν την ενέργεια του παιχνιδιου;

• Τι συνέβη όταν προσπαθήσατε να το κάνετε αυτό (μνμ σφάλματος, μνμ στην μπάρα κατάστασης, ...);

• Ποιο είναι το πρόγραμμα περιήγησής σου;

• Σε ποια φάση του παιχνιδιού προέκυψε το πρόβλημα (ποιά ήταν η τρέχουσα οδηγία στο παιχνίδι);

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

• Τι συνέβη όταν προσπαθήσατε να κάνετε κάποια ενέργεια στο παιχνίδι (μνμ σφάλματος, μνμ στην μπάρα κατάστασης, ...);

• Ποιο είναι το πρόγραμμα περιήγησής σου;

• Παρακαλούμε περιγράψτε το πρόβλημα απεικόνισης που έχετε. Αν έχεις απόσπασμα οθόνης από αυτό το σφάλμα (είναι καλή αυτή η πρακτική), μπορείς να χρησιμοποιήσεις το 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!

• Ποιο είναι το πρόγραμμα περιήγησής σου;

• Παρακαλώ κάνε αντιγραφή/επικόλληση του κειμένου που απεικονίζεται στα αγγλικά αντί για αυτό που είναι στη γλώσσα σου.. Αν έχεις απόσπασμα οθόνης από αυτό το σφάλμα (είναι καλή αυτή η πρακτική), μπορείς να χρησιμοποιήσεις το 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 ώρες;

• Ποιο είναι το πρόγραμμα περιήγησής σου;

• Παρακάλώ εξηγήστε την πρότασή σας με ακρίβεια και περιεκτικότητα, ώστε να είναι όσο το δυνατόν πιο εύκολο να γίνει αντιληπτό τι εννοείτε.

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

• Ποιο είναι το πρόγραμμα περιήγησής σου;