Scripted trigger

admin_governor_allows_declaring_war_trigger

admin_governor_allows_declaring_war_trigger = yes

game/common/scripted_triggers/00_war_and_peace_triggers.txt, line 223 (6 lines). No parameters.

admin_governor_allows_declaring_war_trigger is a scripted trigger in Crusader Kings III, written at line 223 of its file. It takes no parameters: admin_governor_allows_declaring_war_trigger = yes (or no). The game's script calls it in 1 place, among them allows_declaring_war_against_target_trigger (scripted trigger). Patch 1.20.1.2, from game/common/scripted_triggers/00_war_and_peace_triggers.txt.

What it checks

One of these
- vassal_contract_has_flag = admin_theme_frontier
- or
  vassal_contract_has_flag = admin_theme_naval

• 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 (6 lines of game script)

admin_governor_allows_declaring_war_trigger = {
	OR = {
		vassal_contract_has_flag = admin_theme_frontier
		vassal_contract_has_flag = admin_theme_naval
	}
}

As written in game/common/scripted_triggers/00_war_and_peace_triggers.txt.

Where it is used

Every place in common/, events/ and history/ that calls admin_governor_allows_declaring_war_trigger.

Scripted triggers (1)

allows_declaring_war_against_target_trigger

Source: game/common/scripted_triggers/00_war_and_peace_triggers.txt and every file of common/, events/ and history/ that calls it, Crusader Kings III 1.20.1.2.