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

Scripted trigger

can_be_spymaster_trigger

can_be_spymaster_trigger = { COURT_OWNER = … }

game/common/scripted_triggers/00_councillor_triggers.txt, line 115 (15 lines). Parameters: $COURT_OWNER$.

can_be_spymaster_trigger is a scripted trigger in Crusader Kings III, written at line 115 of its file. A call passes 1 parameter: COURT_OWNER. The game's script calls it in 13 places, among them Ask for Council Position (interaction), Demand Council Position (interaction) and Raid for Captives (casus belli). Patch 1.20.1.2, from game/common/scripted_triggers/00_councillor_triggers.txt.

What it checks

  • can_be_councillor_basics_trigger = yes
  • Not all of these

    • has_council_position = councillor_court_chaplain
    • Their rite: The rite has The Realm Priest or Court Chaplain have their seat for life
  • None of these

    • has_council_position = councillor_spouse
    • All of these

      • this = liege.diarch
      • Their liege:
        • has_diarchy_active_parameter = diarchy_is_vizierate

• 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 (15 lines of game script)
can_be_spymaster_trigger = {
	can_be_councillor_basics_trigger = yes
	NAND = {
		has_council_position = councillor_court_chaplain
		rite = { rite_has_parameter = clerical_appointment_fixed }
	}
	NOR = {
		has_council_position = councillor_spouse
		AND = {
			this = liege.diarch
			liege = { has_diarchy_active_parameter = diarchy_is_vizierate }
		}
	}
	exists = $COURT_OWNER$ #so we can have the argument but get no errors
}

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

Where it is used

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

Events (4)

Scripted triggers inside an event file (2)

  • intrigue_temptation_3120_temptable_guests
  • lover_1006_lover_council_position_trigger

Council positions (1)

  • Spymaster

Courtier guest management (1)

  • guest_management

Source: game/common/scripted_triggers/00_councillor_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?