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

Scripted trigger

ep3_negotiate_settlement_valid_county_trigger

ep3_negotiate_settlement_valid_county_trigger = yes

game/common/scripted_triggers/00_laamp_triggers.txt, line 292 (15 lines). No parameters.

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

What it checks

  • One of these

    • holder = scope:actor
    • or

      If

      • scope:actor: they has administrative government mechanic

      Then

      • Their holder:
        • target_is_liege_or_above = scope:actor
  • NOT = { holder.capital_county ?= this }
  • NOT = { holder.primary_title ?= this }

• 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)
ep3_negotiate_settlement_valid_county_trigger = {
	OR = {
		holder = scope:actor
		trigger_if = {
			limit = {
				scope:actor = { government_has_mechanic = administrative }
			}
			holder = { target_is_liege_or_above = scope:actor }
		}
	}
	NOR = {
		holder.capital_county ?= this
		holder.primary_title ?= this
	}
}

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

Where it is used

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

Character interactions (1)

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