Scripted trigger
petition_liege_fortify_border_trigger
petition_liege_fortify_border_trigger = yesgame/common/scripted_triggers/00_activity_triggers.txt, line 229 (15 lines). No parameters.
petition_liege_fortify_border_trigger is a scripted trigger in Crusader Kings III, written at line 229 of its file. It takes no parameters: petition_liege_fortify_border_trigger = yes (or no). The game's script calls it in 3 places, among them Petition the … (decision), petition_liege.9000 (event) and Petition: Switching Tactics (event petition_liege.9001). Patch 1.20.1.2, from game/common/scripted_triggers/00_activity_triggers.txt.
The comment above it in the file
Fortify
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 (15 lines of game script)
petition_liege_fortify_border_trigger = {
tier = tier_county
trigger_if = {
limit = { tier = tier_county }
county = {
save_temporary_scope_as = county_scope
any_title_to_title_neighboring_county = {
holder.top_liege != scope:county_scope.holder.top_liege # petition_liege
NOT = {
holder.top_liege = { is_allied_to = scope:county_scope.holder.top_liege } # petition_liege
}
}
}
}
}As written in game/common/scripted_triggers/00_activity_triggers.txt.
Where it is used
Every place in common/, events/ and history/ that calls petition_liege_fortify_border_trigger.
Decisions (1)
Events (2)
- petition_liege.9000
- Petition: Switching Tactics
petition_liege.9001
Source: game/common/scripted_triggers/00_activity_triggers.txt and every file of common/, events/ and history/ that calls it, Crusader Kings III 1.20.1.2.