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

Scripted trigger · Roads to Power files

ep3_boundary_dispute_county_trigger

ep3_boundary_dispute_county_trigger = { OWNER = … TARGET = … }

game/common/scripted_triggers/07_ep3_triggers.txt, line 1240 (18 lines). Parameters: $OWNER$, $TARGET$.

ep3_boundary_dispute_county_trigger is a scripted trigger in Crusader Kings III, in the Roads to Power files, written at line 1240 of its file. A call passes 2 parameters: OWNER and TARGET. The game's script calls it in 1 place, among them Boundary Dispute (Scheme) (interaction). Its body carries 1 text of the game's own for the player. Patch 1.20.1.2, from game/common/scripted_triggers/07_ep3_triggers.txt.

What it checks

• 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 (18 lines of game script)
ep3_boundary_dispute_county_trigger = {
	tier = tier_county
	custom_tooltip = {
		text = dispute_border_county_neighbour_tt
		county_held_or_vassal_to_target_trigger = { TARGET = $TARGET$ }
		OR = {
			any_neighboring_county = {
				county_held_or_vassal_to_target_trigger = { TARGET = $OWNER$ }
			}
			AND = {
				de_jure_liege.holder ?= $OWNER$
				any_title_to_title_neighboring_and_across_water_county = {
					county_held_or_vassal_to_target_trigger = { TARGET = $OWNER$ }
				}
			}
		}
	}
}

As written in game/common/scripted_triggers/07_ep3_triggers.txt.

Where it is used

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

Character interactions (1)

Source: game/common/scripted_triggers/07_ep3_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?