Scripted trigger · By God Alone files
pam_demand_child_recipient_cares_trigger
pam_demand_child_recipient_cares_trigger = yesgame/common/scripted_triggers/pam_scripted_triggers.txt, line 3015 (9 lines). No parameters.
pam_demand_child_recipient_cares_trigger is a scripted trigger in Crusader Kings III, in the By God Alone files, written at line 3015 of its file. It takes no parameters: pam_demand_child_recipient_cares_trigger = yes (or no). The game's script calls it in 1 place, among them Demand Child for the Cloister (interaction). Patch 1.20.1.2, from game/common/scripted_triggers/pam_scripted_triggers.txt.
The comment above it in the file
Used by demand_child_as_monk_interaction. True if scope:recipient genuinely cares about losing scope:secondary_recipient, either their own direct child, or any child betrothed to one of their close family members.
What it checks
One of these
scope:secondary_recipient:is_child_of = scope:recipient
or
scope:secondary_recipient:exists = betrothed- Their betrothed:
is_close_family_of = scope:recipient
• 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 (9 lines of game script)
pam_demand_child_recipient_cares_trigger = {
OR = {
scope:secondary_recipient = { is_child_of = scope:recipient }
scope:secondary_recipient = {
exists = betrothed
betrothed = { is_close_family_of = scope:recipient }
}
}
}As written in game/common/scripted_triggers/pam_scripted_triggers.txt.
Where it is used
Every place in common/, events/ and history/ that calls pam_demand_child_recipient_cares_trigger.
Character interactions (1)
Source: game/common/scripted_triggers/pam_scripted_triggers.txt and every file of common/, events/ and history/ that calls it, Crusader Kings III 1.20.1.2.