CK3 DatabaseCrusader Kings III · 1.20.1.2 “Crozier” · unofficial
Silk & Silverout Tue, Nov 17What's free, what needs the DLC, price →

Scripted trigger

actor_has_capital_archbishop_trigger

actor_has_capital_archbishop_trigger = yes

game/common/scripted_triggers/00_religious_triggers.txt, line 3431 (10 lines). No parameters.

actor_has_capital_archbishop_trigger is a scripted trigger in Crusader Kings III, written at line 3431 of its file. It takes no parameters: actor_has_capital_archbishop_trigger = yes (or no). The game's script calls it in 3 places, among them Ask for Gold (interaction), Seek Indulgences (interaction) and seek_indulgences_recipient_trigger (scripted trigger). Patch 1.20.1.2, from game/common/scripted_triggers/00_religious_triggers.txt.

The comment above it in the file

Actor scope: capital region archbishops resolve to themselves and do not count

What it checks

  • If

    a check the game hides

    Then

    • Their capital county’s clerical region’s holder: Their faith is the same as that of actor

    Otherwise

    • 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 (10 lines of game script)
actor_has_capital_archbishop_trigger = {
	trigger_if = {
		limit = { exists = capital_county.clerical_region_title.holder }
		capital_county.clerical_region_title.holder = {
			NOT = { this = scope:actor }
			faith = scope:actor.faith
		}
	}
	trigger_else = { always = no }
}

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

Where it is used

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

Character interactions (2)

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

Spotted a mistake on this page?