Scripted trigger
gather_debug_variables_for_persian_struggle_trigger
gather_debug_variables_for_persian_struggle_trigger = yesgame/common/scripted_triggers/00_generic_struggle_scripted_triggers.txt, line 7 (1 lines). No parameters.
gather_debug_variables_for_persian_struggle_trigger is a scripted trigger in Crusader Kings III, written at line 7 of its file. It takes no parameters: gather_debug_variables_for_persian_struggle_trigger = yes (or no). The game's script calls it in 4 places, among them Iranian Intermezzo (struggle), on_game_start (on action) and fp3_end_persian_struggle_effect (scripted effect). Patch 1.20.1.2, from game/common/scripted_triggers/00_generic_struggle_scripted_triggers.txt.
The comment above it in the file
Do we want to gather global variable tallies for the Persian struggle? Toggled off for release, toggle back on to check how often we change phases & which catalysts are firing.
What it checks
- Never
• the game's own tooltip text · ◦ our reading of the script line · code the script where neither exists
“They” is whatever it runs on (the scope it is called in). The scripted triggers and effects it calls link to their own pages; $PARAMETERS$ stay as written: each call fills them in.
The script as written (1 line of game script)
gather_debug_variables_for_persian_struggle_trigger = { always = no }As written in game/common/scripted_triggers/00_generic_struggle_scripted_triggers.txt.
Where it is used
Every place in common/, events/ and history/ that calls gather_debug_variables_for_persian_struggle_trigger.
Struggles (1)
- Iranian Intermezzo
On actions (the game's own hooks) (1)
- on_game_start
Scripted effects (2)
Source: game/common/scripted_triggers/00_generic_struggle_scripted_triggers.txt and every file of common/, events/ and history/ that calls it, Crusader Kings III 1.20.1.2.