It was my mistake; I meant adding something like Battleodds < 0.75 or Battleodds < 0.51 for that case.
Regarding the "warrior commander" who fights all battles, I feel that this case is covered by trigger battle_coward1, where the general -whether his army was retreating or not- gave battle and lost without risking himself; in this case, yes, I accept he should be regarded as a coward.
Definetely, retreating "uncowardly" was the norm for armies that were applying hit-and-run tactics, like raiding armies or armies trying to distract a major enemy force (for example, when defending own territory and waiting for reinforcements or gathering forces). But, I know, this discussion is not suitable for this thread.
Besides, there is also the Trigger battle3Chivalry1_notchaserouters
Code:
Trigger battle3Chivalry1_notchaserouters
WhenToTest PostBattle
Condition WonBattle
and BattleSuccess >= average
and PercentageEnemyKilled < 10
and not GeneralFoughtInCombat
and IsGeneral
and BattleOdds < 0.95
and not Trait BattleDread > 0
Affects BattleChivalry 1 Chance 33
Code:
Trigger battle_coward2
WhenToTest PostBattle
Condition not GeneralFoughtInCombat
and PercentageEnemyKilled = 0
Affects Coward 1 Chance 10
So, postbattle, a general -if he didn't fought in combat and no enemy was killed- can acquire both BattleChivalry and Coward points, which seems, at least to me, quite contradicting.
This cowardly acquiring of chivalry (and being chivalriously coward) did happened once for a general of mine -it was a siege attack, I had only the general and his bodyguards, the defenders lacked cavalry, I lured them out and far from their settlement and then ran to the castle center, the defenders didn't manage to keep up as they got exhausted by chasing my cavalry unit, so I kept control of the square till time ran out; I found it hilarious too.
So, I believe that, for the trigger battle_coward2, both conditions "notWonBattle" and "Battleodds < 0.51" or like should be added.
I like that! I had commented out one of these triggers for my own play, but now I'll do just as you said. However, the fix I suggested in my previous post has exactly the same effects as the inclusion of both triggers as they are but "consumes less CPU cycles" (sorry, no more appropriate phrase came in my mind).
I like that too. I feel, however, that this case is covered in Trigger battle2a, where the general not only involved in combat, which could have happened even against his own will, but stayed and made some kills too.
I prefer this trigger being commented out, as with so many triggers affecting trait brave, generals are getting too brave for my taste. Of course, this is not any kind of "demand" for the bugfix compilation [by the way, it's a great work, I 'd like to spread reputation(?), but I don't know how]; it's not critical.
Code:
Trigger battle2a
WhenToTest PostBattle
Condition GeneralNumKillsInBattle > 6
Affects Brave 1 Chance 15
Cowardly Chivalrous? How properly tweak these trait triggers
Originally Posted by gsthoed
Reply With Quote
