List of non or mal functioning script terms (events, conditions and commands)

[Jadli]

I mean after battle. In that moment, the armies are already on the run/dead, and it didnt crash no matter how many armies were originally there afaik..

[Gigantus]

Hence why I linked to both references in the OP. battle script = crash reported with more then 2 armies. campaign script = apparently fine all along.

[Jadli]

Well, no, it still crashed for me when used before battle. But after battle it worked fine, and I believe it counted corretly the amount of of survivors

[Gigantus]

NumEnemiesInBattle doesn't count survivors, it counts initial enemy combatants afaik.

[Jadli]

I found out that if you want to disable a hortcut permanently, its bugged in a very unfortunate way

If you for example wanted to disable the backspace shortcut, this

disable_shortcuts strat_ui stop_character true

(written anywhere in the script outside of any monitor)

or this

monitor_event GameReloaded
 
 campaign_wait 0.1
 disable_shortcuts strat_ui stop_character true
 
end_monitor

works correctly only the moment you start the campaign. But once you save the game, and load the save from this campaign, all other shortcuts are disabled (quicksaving, space, etc), hence a huge issue.

Apparently there is some bug with this kind of command, in the process of saving it likely disables all shortcut together...

So the solution is this

monitor_event GameReloaded
 
 campaign_wait 0.1
 disable_shortcuts false
 campaign_wait 0.1
 disable_shortcuts strat_ui stop_character true
 
end_monitor

i.e., reenablaing all the shortcuts every time you load the game, and then disable the specific shortcut you want

[z3n]

toggle_perfect_spy could be added to the list: toggle_perfect_spy - only works in script although it needs to be prefixed with console_command

[Callistonian]

terminate_battle - another for the list, I can confirm that it terminates the entire campaign script and it has been reported by Withwnar.

[Belovèse]

Guys, I made some tests that contradict what is said in the OP about I_ConflictType. The short version: for the player testing I_ConflictType gives the intended results. I did not test for the AI, and I did not test the conflict type Withdrawal as it is a bit harder to set up reliably.

I made the test in a simplified version of Bare Geomod : no scripts in CS except my test. Iengaged in all the types of battle except Withdrawal, and every time the log showed the right message and only that one.

the testing script:

monitor_event PostBattle not IsFactionAIControlled
	log ==============================================================================================================================
	log A BATTLE IS TESTED
end_monitor

; WORKS AS INTENDED
monitor_event PostBattle I_ConflictType SuccessfulAmbush
and not IsFactionAIControlled
	log --- CONFLICT TYPE ==> SuccessfulAmbush
end_monitor

; WORKS AS INTENDED
monitor_event PostBattle I_ConflictType FailedAmbush
and not IsFactionAIControlled
	log --- CONFLICT TYPE ==> FailedAmbush
end_monitor

; WORKS AS INTENDED
monitor_event PostBattle I_ConflictType Normal
and not IsFactionAIControlled
	log --- CONFLICT TYPE ==> Normal
end_monitor

; WORKS AS INTENDED
monitor_event PostBattle I_ConflictType Siege
and not IsFactionAIControlled
	log --- CONFLICT TYPE ==> Siege
end_monitor

; WORKS AS INTENDED
monitor_event PostBattle I_ConflictType SallyBesieger
and not IsFactionAIControlled
	log --- CONFLICT TYPE ==> SallyBesieger
end_monitor

; WORKS AS INTENDED
monitor_event PostBattle I_ConflictType Naval
and not IsFactionAIControlled
	log --- CONFLICT TYPE ==> Naval
end_monitor

; PARTIALLY TESTED
; if you withdraw during battle, I_ConflictType is still Normal
; my guess is Withdraw triggers when you flee from one battle and trigger another battle when withdrawing --- Belovese 
monitor_event PostBattle I_ConflictType Withdraw
and not IsFactionAIControlled
	log --- CONFLICT TYPE ==> Withdraw
end_monitor

If you want to download the CS to try yourself, or even the entire set-up I made a gitlab where I host my tests: https://gitlab.com/Belovese/modder_s...ref_type=heads

So in conclusion I would suggest someone try to replicate the result I had, and if it confirms it the OP should be updated.

EDIT: my guess is that it was reported bugged because "I_ConflictType bananas" returns "true", but AFAIK any invalid condition test returns "true" in med2 scripting.

[Gigantus]

I made a note in the OP regarding your results. I assume from your description that only ever one log message was listed in the log, hence proving the condition works provided the value is correct?

[Belovèse]

Yes, exactly, only one log message for every battle involving the player.

Thanks for the note in the op!

[Gigantus]

Updated with I_SoundPlaying condition findings.