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

has_been_promised_grand_wedding

has_been_promised_grand_wedding = yes

game/common/scripted_triggers/04_ep2_wedding_triggers.txt, line 12 (3 lines). No parameters.

has_been_promised_grand_wedding is a scripted trigger in Crusader Kings III, in the Tours and Tournaments files, written at line 12 of its file. It takes no parameters: has_been_promised_grand_wedding = yes (or no). The game's script calls it in 26 places, among them Arrange Marriage (interaction), Break Betrothal (interaction) and Demand Child for the Cloister (interaction). Patch 1.20.1.2, from game/common/scripted_triggers/04_ep2_wedding_triggers.txt.

What it checks

  • Has “promised grand wedding by” (a variable the game's script sets)

• 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 (3 lines of game script)
has_been_promised_grand_wedding = {
	has_variable = promised_grand_wedding_by
}

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

Where it is used

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

Activities (1)

Important actions (2)

  • Betrothed can Marry
  • Betrothed can Marry in Grand Wedding

Scripted effects inside an event file (1)

  • send_bethrothal_notifications_and_apply_opinions_effect

Scripted triggers inside an event file (1)

  • valid_runaway_character_trigger

Scripted modifiers (AI weights) (1)

  • marriage_ai_accept_modifier

Scripted rules (1)

  • can_be_activity_guest

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