Scripted trigger · Khans of the Steppe files

mpo_settlement_issue_trigger

mpo_settlement_issue_trigger = { NUMBER = … }

game/common/scripted_triggers/09_mpo_settlement_issue_triggers.txt, line 42 (16 lines). Parameters: $NUMBER$ .

mpo_settlement_issue_trigger is a scripted trigger in Crusader Kings III, in the Khans of the Steppe files, written at line 42 of its file. A call passes 1 parameter: NUMBER. The game's script calls it in 5 places, among them mpo_contract_events.0001 (event), mpo_contract_events.0011 (event) and mpo_contract_events.0031 (event). Patch 1.20.1.2, from game/common/scripted_triggers/09_mpo_settlement_issue_triggers.txt.

What it checks

Knight (at least 1):
Any held county:
- is_landless_type_title = no
- County Control less than 90
- The county does not have the modifier “Ongoing Settlement Contract”
None of these
- Any task contract:
  - has_task_contract_type = nomadic_migration_contract_$NUMBER$

• 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 (16 lines of game script)

mpo_settlement_issue_trigger = {
	any_knight = {
		count >= 1
	}
	any_held_county = {
		is_landless_type_title = no
		exists = title_province
		county_control < 90
		NOT = { has_county_modifier = ongoing_settlement_contract }
	}
	NOT = {
		any_task_contract = {
			has_task_contract_type = nomadic_migration_contract_$NUMBER$
		}
	}
}

As written in game/common/scripted_triggers/09_mpo_settlement_issue_triggers.txt.

Where it is used

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

Events (5)

Source: game/common/scripted_triggers/09_mpo_settlement_issue_triggers.txt and every file of common/, events/ and history/ that calls it, Crusader Kings III 1.20.1.2.