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

thug_attribute_acceptable_trigger

thug_attribute_acceptable_trigger = yes

game/common/scripted_triggers/04_ep2_accolade_triggers.txt, line 706 (15 lines). No parameters.

thug_attribute_acceptable_trigger is a scripted trigger in Crusader Kings III, in the Tours and Tournaments files, written at line 706 of its file. It takes no parameters: thug_attribute_acceptable_trigger = yes (or no). The game's script calls it in 1 place, among them Thug (accolade types). Patch 1.20.1.2, from game/common/scripted_triggers/04_ep2_accolade_triggers.txt.

What it checks

  • One of these

    • Ai honor at most -20
    • or

      Ai rationality at most -20
    • or

      Has the Trait: Pillager
  • Does not have the Trait: Calm
  • Does not have the Trait: Just
  • Does not have the Trait: Patient
  • Does not have the Trait: Humble
  • Ai compassion at most 0
  • Ai honor at most 0

• 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 (15 lines of game script)
thug_attribute_acceptable_trigger = {
	OR = {
		ai_honor <= low_negative_ai_value
		ai_rationality <= low_negative_ai_value
		has_trait = reaver
	}
	NOR = {
		has_trait = calm
		has_trait = just
		has_trait = patient
		has_trait = humble
		ai_compassion > 0
		ai_honor > 0
	}
}

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 thug_attribute_acceptable_trigger.

Accolade types (1)

  • Thug

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?