So a long time ago Paradox removed in-combat attrition. Last patch they removed (or intensely nerfed) rotating your troops out and back in to a battle. In my opinion these two changes have made made multiplayer wars and large AI wars very tedious. They come down to both sides doomstacking 200k+ troops in to a battle, and then watching for months as the battle resolves itself. All strategic play is removed, and enjoyable positioning and repositioning for sieges/better fights has been removed. While troop rotating wasn't THAT exciting, it was at least something to do while doomstacks duked it out.
I think in-combat attrition was removed to begin with because the AI never quite understood it and would stack their entire army in to a battle and get attrition to oblivion, however I don't think a fix for that is THAT hard, and adding back in-combat attrition would do a lot to make the game play a lot more historically (how many wars were one-front giant 300k vs. 300k fights?) Also, since the AI often fails to understand doomstacking and will put armies EVERYWHERE it might help them actually be competent in the face of player doomstacking.
In-combat attrition would bring back punishing doomstacking . Right now worst case scenario is you take one tick of 5% attrition before splitting up your armies post-battle and lose a grand total of like 10k troops after winning a battle. It would mean holding up a mountain/hill/etc. with a smaller army against a larger one would actually be a good decision, as the opponents while still likely winning would take attrition the whole way making it a costly move.
If not in-combat attrition then maybe some other mechanics to punish doomstacking? Reducing siege timers by 15-20% for example so people can actually complete sieges before the rotating doomstack pushes everyone back. (I also think reducing siege timers would be good overall for the entire game, both for historical sake and for sanity sake.) Or maybe attrition that only starts to trigger when above 100k troops, though that would be a bandaid.
I think Victoria 2 has the best combat system of the Vicky2 CK2 EU4 set, and EU4 should try best to emulate it, as an aside. Watch any AAR of EU4 multiplayer and Vicky2 multiplayer and you'll see how much more interesting the Vicky2 wars are.
I think in-combat attrition was removed to begin with because the AI never quite understood it and would stack their entire army in to a battle and get attrition to oblivion, however I don't think a fix for that is THAT hard, and adding back in-combat attrition would do a lot to make the game play a lot more historically (how many wars were one-front giant 300k vs. 300k fights?) Also, since the AI often fails to understand doomstacking and will put armies EVERYWHERE it might help them actually be competent in the face of player doomstacking.
In-combat attrition would bring back punishing doomstacking . Right now worst case scenario is you take one tick of 5% attrition before splitting up your armies post-battle and lose a grand total of like 10k troops after winning a battle. It would mean holding up a mountain/hill/etc. with a smaller army against a larger one would actually be a good decision, as the opponents while still likely winning would take attrition the whole way making it a costly move.
If not in-combat attrition then maybe some other mechanics to punish doomstacking? Reducing siege timers by 15-20% for example so people can actually complete sieges before the rotating doomstack pushes everyone back. (I also think reducing siege timers would be good overall for the entire game, both for historical sake and for sanity sake.) Or maybe attrition that only starts to trigger when above 100k troops, though that would be a bandaid.
I think Victoria 2 has the best combat system of the Vicky2 CK2 EU4 set, and EU4 should try best to emulate it, as an aside. Watch any AAR of EU4 multiplayer and Vicky2 multiplayer and you'll see how much more interesting the Vicky2 wars are.
- 7