Quote Originally Posted by Bob the Insane
But, one thing I noted with the example you provide, it will not trigger coward for simply withdrawing from the battlefield immediately (on the battlemap). Where GeneralNumKillsInBattle = 0 and PercentageEnemyKilled = 0 (I presume)... Was this intentional?
Player1's fixes to my attempt at solving the coward bug seem to be the best option. Generalfoughtincombat seems to be totally buggered. This could be affecting the Heroic Saviour ancilliary too, which should be changed to GeneralNumKillsInBattle > 0.

To answer your question, it will not trigger if you withdraw, BUT that isn't what the coward trait is about.
There's another trait (indecisive attacker) and 3 triggers which cover withdrawing before combat (100% chance when you are the attacker, 50% chance when odds are 0.8-1.5 and a 50% chance for a 2-step increase when odds >3). It has huge thresholds though (8, 16, 32) and has goodcommander and goodattacker as antitraits, so it's hardly ever seen.
Strangely, if odds are 1.5-3 and you aren't attacking, it's safe to withdraw - another trait glitch!
Therefore, in Trigger V0200, the > 3 should be reduced to > 1.5. If you want coward traits to be added, then put "coward 1 chance 50" in Trigger V0200, which would now fire when odds >1.5 and you withdraw. You could put "coward 1 chance 10" in Trigger V0190 as well, if you want to really persecute generals who avoid battle when they have a good chance of winning!
The only problem is that I don't know how often the AI general withdraws. If he withdraws a lot (he did in MTW) then he could be heavily penalised by coward traits. That might even be the reason why "indecisive attacker" has such high thresholds.