Scripted trigger
clerical_chastity_recipient_realm_borders_actor_trigger
clerical_chastity_recipient_realm_borders_actor_trigger = yesgame/common/scripted_triggers/clerical_chastity_triggers.txt, line 24 (11 lines). No parameters.
clerical_chastity_recipient_realm_borders_actor_trigger is a scripted trigger in Crusader Kings III, written at line 24 of its file. It takes no parameters: clerical_chastity_recipient_realm_borders_actor_trigger = yes (or no). The game's script calls it in 1 place, among them clerical_chastity_recipient_valid_for_actor_scope_trigger (scripted trigger). Patch 1.20.1.2, from game/common/scripted_triggers/clerical_chastity_triggers.txt.
What it checks
- scope:puppet_or_actor › Any sub realm county: Any neighboring county:
• 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 (11 lines of game script)
clerical_chastity_recipient_realm_borders_actor_trigger = {
scope:puppet_or_actor = {
any_sub_realm_county = {
any_neighboring_county = {
holder = {
this = scope:recipient
}
}
}
}
}As written in game/common/scripted_triggers/clerical_chastity_triggers.txt.
Where it is used
Every place in common/, events/ and history/ that calls clerical_chastity_recipient_realm_borders_actor_trigger.
Scripted triggers (1)
Source: game/common/scripted_triggers/clerical_chastity_triggers.txt and every file of common/, events/ and history/ that calls it, Crusader Kings III 1.20.1.2.