Scripted trigger

courtier_or_guest_claim_trigger

courtier_or_guest_claim_trigger = { RULER = … }

game/common/scripted_triggers/00_courtier_guest_management_triggers.txt, line 579 (11 lines). Parameters: $RULER$ .

courtier_or_guest_claim_trigger is a scripted trigger in Crusader Kings III, written at line 579 of its file. A call passes 1 parameter: RULER. The game's script calls it in 4 places, among them neighboring_useful_courtier_or_guest_claim_trigger (scripted trigger), useful_courtier_or_guest_claim_trigger (scripted trigger) and individual_recruit_guest_interaction_cost (script value). Patch 1.20.1.2, from game/common/scripted_triggers/00_courtier_guest_management_triggers.txt.

The comment above it in the file

GUEST/COURTIER USEFULNESS TRIGGERS###

What it checks

None of these
- Their holder:
  - One of these
    this = $RULER$
    or
    target_is_liege_or_above = $RULER$

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

courtier_or_guest_claim_trigger = {
	exists = holder
	NOT = {
		holder = {
			OR = {
				this = $RULER$
				target_is_liege_or_above = $RULER$
			}
		}
	}
}

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

Where it is used

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

Scripted triggers (2)

Script values (1)

individual_recruit_guest_interaction_cost

Courtier guest management (1)

guest_management

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