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

Scripted trigger

bannable_serving_diarch_trigger

bannable_serving_diarch_trigger = yes

game/common/scripted_triggers/00_diarchy_scripted_triggers.txt, line 130 (19 lines). No parameters.

bannable_serving_diarch_trigger is a scripted trigger in Crusader Kings III, written at line 130 of its file. It takes no parameters: bannable_serving_diarch_trigger = yes (or no). The game's script calls it in 47 places, among them Chariot Race (activity), Ecumenical Council (activity) and Grand Tournament (activity). Patch 1.20.1.2, from game/common/scripted_triggers/00_diarchy_scripted_triggers.txt.

The comment above it in the file

And *this* needs to be added to guest activity intents to keep diarchs from showing up to the same parties as their liege.

What it checks

  • Their liege:
  • One of these

    • is_diarch = yes
    • or

      is_designated_diarch = yes
    • or

      All of these

      • Is played by the AI
      • is_diarchy_successor = 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 (19 lines of game script)
bannable_serving_diarch_trigger = {
	liege ?= {
		NOR = {
			is_landless_adventurer = yes
			has_diarchy_type = grand_secretariat
		}
	}
	OR = {
		# Diarchs with official responsibilities can't come out to play.
		is_diarch = yes
		is_designated_diarch = yes
		# Assumed diarchs don't get to either if they're the AI, as the player might be planning around them & the AI may have designated to avoid people after if it'd known they were going to welch.
		## Assumed-diarch players can make an intelligent choice on whether they want to go to events or not.
		AND = {
			is_ai = yes
			is_diarchy_successor = yes
		}
	}
}

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

Where it is used

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

Activity intents (1)

  • Support Entrants

Court positions (1)

Events (1)

Scripted effects inside an event file (1)

  • travel_event_1060_grab_local_pilgrims_effect

Scripted triggers (1)

Script values (5)

  • hunt_entourage_base_set_weighting_value
  • pilgrimage_entourage_base_set_weighting_value
  • pilgrimage_entourage_extras_set_weighting_value
  • pilgrimage_entourage_sodding_everyone_set_weighting_value
  • standard_travel_entourage_additions

Customizable localization (1)

  • GetInviteToActivityFlavor

Activities (31)

  • All Lieges
  • Clergy
  • Close Family
  • Confederates
  • Court Guests
  • Court Hunters
25 more
  • Courtiers
  • Crushes
  • Extended Family
  • Fellow Vassals
  • Friends
  • Glory Hound Vassals
  • Head of Faith
  • Heir
  • House
  • Knights
  • Liege
  • Lovers
  • Neighboring Rulers
  • Other
  • Potential Friends
  • Potential Lovers
  • Rivals
  • Rivals
  • Scheme Targets
  • Siblings
  • Spouses' Close Family
  • Spouses' Extended Family
  • Suzerain
  • Tributaries
  • Vassals

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