Scripted trigger

should_in_default_location_trigger

should_in_default_location_trigger = yes

game/common/scripted_triggers/00_available_for_events_triggers.txt, line 1003 (9 lines). No parameters.

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

What it checks

Is available (not in an army, not imprisoned)

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

should_in_default_location_trigger = {
	is_available_quick = {
		alive = yes
		travel = no
		in_army = no
		imprisoned = no
	}
	NOT = { exists = involved_activity }
}

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

Where it is used

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

Scripted effects (1)

update_domicile_and_courtier_location_effect

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