Scripted trigger · The Fate of Iberia files
purchase_truce_interaction_recipient_can_de_jure_war_actor_trigger
purchase_truce_interaction_recipient_can_de_jure_war_actor_trigger = yesgame/common/scripted_triggers/03_fp2_scripted_triggers.txt, line 144 (18 lines). No parameters.
purchase_truce_interaction_recipient_can_de_jure_war_actor_trigger is a scripted trigger in Crusader Kings III, in the The Fate of Iberia files, written at line 144 of its file. It takes no parameters: purchase_truce_interaction_recipient_can_de_jure_war_actor_trigger = yes (or no). The game's script calls it in 1 place, among them Purchase Truce (interaction). Patch 1.20.1.2, from game/common/scripted_triggers/03_fp2_scripted_triggers.txt.
What it checks
scope:recipient:One of these
has_cb_on = { target = scope:actor cb = de_jure_cb }or
has_cb_on = { target = scope:actor cb = individual_county_de_jure_cb }or
has_cb_on = { target = scope:actor cb = individual_duchy_de_jure_cb }
• 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 (18 lines of game script)
purchase_truce_interaction_recipient_can_de_jure_war_actor_trigger = {
scope:recipient = {
OR = {
has_cb_on = {
target = scope:actor
cb = de_jure_cb
}
has_cb_on = {
target = scope:actor
cb = individual_county_de_jure_cb
}
has_cb_on = {
target = scope:actor
cb = individual_duchy_de_jure_cb
}
}
}
}As written in game/common/scripted_triggers/03_fp2_scripted_triggers.txt.
Where it is used
Every place in common/, events/ and history/ that calls purchase_truce_interaction_recipient_can_de_jure_war_actor_trigger.
Character interactions (1)
Source: game/common/scripted_triggers/03_fp2_scripted_triggers.txt and every file of common/, events/ and history/ that calls it, Crusader Kings III 1.20.1.2.