If you start a combat against a smaller army, the game deploys the same number of troops on the front row, and then when the AI sends in reinforcement and fills up the combat width, my army still stays away from the corner squares that were initially left empty and get flanked for the remainder of the battle. This is worse if you have artillery; unlike infantry, cannons move up to the front row when fighting against smaller stack and then when reinforcement arrive get caught in melee and the entire formation breaks down (no artillery back row support, cannons taking damage, etc). To avoid this I need to do as below.
1. An enemy army smaller than combat width sieging down my occupied fort in Groningen. If I send in my main combat force directly, my cannons will get caught by enemy reinforcement as I've described above. So instead I need to first send in the bait 30k infantry army.
2. It's difficult to see because of Prussia's color, but the flanks are left empty even though I have enough troops to cover them.
3. Flanks still left open, retreat possible at 6th of November.
4. Time my main army to arrive at Groningen at 7th of November.
5. Retreat at 6th, enemy now has enough troops to fill the combat width from the start so my army should deploy correctly.
6. It does this for some reason, guessing it has something to do with re-engaging immediately.
7. Paradox plz fix
1. An enemy army smaller than combat width sieging down my occupied fort in Groningen. If I send in my main combat force directly, my cannons will get caught by enemy reinforcement as I've described above. So instead I need to first send in the bait 30k infantry army.
2. It's difficult to see because of Prussia's color, but the flanks are left empty even though I have enough troops to cover them.
3. Flanks still left open, retreat possible at 6th of November.
4. Time my main army to arrive at Groningen at 7th of November.
5. Retreat at 6th, enemy now has enough troops to fill the combat width from the start so my army should deploy correctly.
6. It does this for some reason, guessing it has something to do with re-engaging immediately.
7. Paradox plz fix