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

Scripted trigger · The Northern Lords files

fp1_county_has_stele_trigger

fp1_county_has_stele_trigger = yes

game/common/scripted_triggers/01_fp1_scripted_triggers.txt, line 33 (10 lines). No parameters.

fp1_county_has_stele_trigger is a scripted trigger in Crusader Kings III, in the The Northern Lords files, written at line 33 of its file. It takes no parameters: fp1_county_has_stele_trigger = yes (or no). The game's script calls it in 1 place, among them fp1_0571_suitable_vandal_site_trigger (local trigger). Patch 1.20.1.2, from game/common/scripted_triggers/01_fp1_scripted_triggers.txt.

What it checks

  • One of these

    • The county has the modifier “Ancestral Runestone”
    • or

      The county has the modifier “Conquest Runestone”
    • or

      The county has the modifier “Clout Runestone”

• 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)
fp1_county_has_stele_trigger = {
	OR = {
		has_county_modifier = fp1_stele_ancestors_strong
		has_county_modifier = fp1_stele_ancestors_weak
		has_county_modifier = fp1_stele_conquest_strong
		has_county_modifier = fp1_stele_conquest_weak
		has_county_modifier = fp1_stele_promotion_strong
		has_county_modifier = fp1_stele_promotion_weak
	}
}

As written in game/common/scripted_triggers/01_fp1_scripted_triggers.txt.

Where it is used

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

Scripted triggers inside an event file (1)

  • fp1_0571_suitable_vandal_site_trigger

Source: game/common/scripted_triggers/01_fp1_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?