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

Scripted trigger

has_intrigue_lifestyle_trait_trigger

has_intrigue_lifestyle_trait_trigger = yes

game/common/scripted_triggers/00_general_trait_triggers.txt, line 1122 (7 lines). No parameters.

has_intrigue_lifestyle_trait_trigger is a scripted trigger in Crusader Kings III, written at line 1122 of its file. It takes no parameters: has_intrigue_lifestyle_trait_trigger = yes (or no). The game's script calls it in 29 places, among them Convert to Witchcraft (scheme), A Way In (event intrigue_scheme_lifestyle.3401) and A Web (event seduce_ongoing.6031). Patch 1.20.1.2, from game/common/scripted_triggers/00_general_trait_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 (7 lines of game script)
has_intrigue_lifestyle_trait_trigger = {
	OR = {
		has_trait = schemer
		has_trait = seducer
		has_trait = torturer
	}
}

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

Where it is used

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

Schemes (1)

  • Convert to Witchcraft

Events (17)

11 more

Scripted triggers inside an event file (1)

  • diplomacy_foreign_special_1022_wants_to_manipulate

Script values (1)

  • odds_convert_to_witchcraft_misc_value

Scripted modifiers (AI weights) (1)

  • religion_adopt_secret_faith_modifier

Customizable localization (4)

  • DeathMessageOutro
  • HeirMessageInterface
  • MatchingConversationSubject
  • MatchingConversationSubject_alone

Source: game/common/scripted_triggers/00_general_trait_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?