Again no, the trait "Doubtful courage" is there for when the units and the general actually rout, ie they engage and run away. We want that trait in...
Due to the engine limitations, we cannot discern the withdraw button and units withdrawing. As I said the engine thinks they rout. If you even listen to them, they start shouting run away etc (the audio files of routing units)...
The latter behaviour of the trait (when you click withdraw and get the trait) is collateral, since it occurs during exploits for us it is a non-issue. Also as I said the only solution, since the engine cannot discern, would be the removal of the trait. Which is there to work when the units actually rout...
I cannot for the life of me make this any clearer...
The trait is for routing, real bonafide routing. If you use the retreat vanilla feature, which is forced routing on the engine, the engine understands that you've routed...
We want the trait to trigger with real routs, unfortunately it gets triggered by the withdraw button, because for the engine it is a rout...
Actually no, the way you posted that paragraph sounded that you use such quirks of the system to gain advantages and suit your tactics...I assume you knew I was talking about finding ways to enjoy a game, despite its limitations, and not me asserting that one should exploit or cheat to win a game
Still I'm in no way saying your playstyle is wrong or right, I merely stated that in our opinion using fresh reinforcements from withdrawn slots is an exploit and we do not tailor the mod around that...
There is no right or wrong playstyle, just we have to pick one to edit the mechanics around it...
When the player avoids the AI-led reinforcements, specifically to micro them, gains an advantage and he's exploiting the engine. Since even the AI's reinforcements get in the battlefield from the start (although on this point it might depend on the PC running the game)...
Still it isn't affected in anyway by the mod, as I said there is the freedom to use them. However in cases as this one, where a working trait has a collateral behaviour during an exploit, we won't remove the trait (had we had the engine tell the difference between rout and withdraw we'd edit that in already: we simply cannot do that)...
Bookmarks