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

Scripted trigger · Tours and Tournaments files

besieger_attribute_trigger

besieger_attribute_trigger = yes

game/common/scripted_triggers/04_ep2_accolade_triggers.txt, line 449 (22 lines). No parameters.

besieger_attribute_trigger is a scripted trigger in Crusader Kings III, in the Tours and Tournaments files, written at line 449 of its file. It takes no parameters: besieger_attribute_trigger = yes (or no). The game's script calls it in 2 places, among them on_county_occupied (on action) and Besieger (accolade types). Its body carries 2 texts of the game's own for the player. Patch 1.20.1.2, from game/common/scripted_triggers/04_ep2_accolade_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 (22 lines of game script)
besieger_attribute_trigger = {
	custom_tooltip = {
		text = besieger_attribute.unlock_tt
		OR = {
			var:besieger_attribute_unlock ?= yes
			has_trait = military_engineer
			has_trait = logistician
		}
	}
	culture ?= { has_innovation = innovation_catapult }
	custom_tooltip = {
		text = single_maa_attribute_allowance
		trigger_if = {
			limit = {
				exists = accolade
			}
			accolade = {
				NOT = { has_accolade_category = men_at_arms }
			}
		}
	}
}

As written in game/common/scripted_triggers/04_ep2_accolade_triggers.txt.

Where it is used

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

On actions (the game's own hooks) (1)

  • on_county_occupied

Accolade types (1)

  • Besieger

Source: game/common/scripted_triggers/04_ep2_accolade_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?