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

Scripted trigger

lock_contracts_from_spawning_in_sahara_trigger

lock_contracts_from_spawning_in_sahara_trigger = yes

game/common/scripted_triggers/00_laamp_triggers.txt, line 536 (8 lines). No parameters.

lock_contracts_from_spawning_in_sahara_trigger is a scripted trigger in Crusader Kings III, written at line 536 of its file. It takes no parameters: lock_contracts_from_spawning_in_sahara_trigger = yes (or no). The game's script calls it in 2 places, among them populate_location_with_contracts_effect (scripted effect) and populate_location_with_special_contracts_effect (scripted effect). Patch 1.20.1.2, from game/common/scripted_triggers/00_laamp_triggers.txt.

The comment above it in the file

We do not spawn contracts in the Sahara without the right CulTrad.

What it checks

  • One of these

    • None of these

      • Their location: Is in the the Sahara region
    • or

      Their culture: The culture has the tradition Saharan Nomads

• 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 (8 lines of game script)
lock_contracts_from_spawning_in_sahara_trigger = {
	OR = {
		NOT = {
			location = { geographical_region = custom_sahara_proper }
		}
		culture = { has_cultural_tradition = tradition_saharan_nomads }
	}
}

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

Where it is used

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

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?