Scripted trigger

can_keep_single_heir_youngest_succession_law_trigger

can_keep_single_heir_youngest_succession_law_trigger = yes

game/common/scripted_triggers/00_law_triggers.txt, line 413 (12 lines). No parameters.

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

What it checks

If has the Ultimogeniture Law:
- One of these
  - can_have_single_heir_youngest_succession_law_trigger = yes
  - or
    historical_succession_access_single_heir_succession_law_youngest_trigger = yes

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

can_keep_single_heir_youngest_succession_law_trigger = {
	# The 'can_keep' triggers are dependent on actually having the law. If they aren't, the trigger breakdown for the player breaks and shows incomplete information.
	trigger_if = {
		limit = {
			has_realm_law = single_heir_succession_law_youngest
		}
		OR = {
			can_have_single_heir_youngest_succession_law_trigger = yes
			historical_succession_access_single_heir_succession_law_youngest_trigger = yes
		}
	}
}

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

Where it is used

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

Laws (1)

Ultimogeniture

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