Scripted trigger
feast_default_participant_including_player_trigger
feast_default_participant_including_player_trigger = yesgame/common/scripted_triggers/00_feast_activity_triggers.txt, line 23 (7 lines). No parameters.
feast_default_participant_including_player_trigger is a scripted trigger in Crusader Kings III, written at line 23 of its file. It takes no parameters: feast_default_participant_including_player_trigger = yes (or no). The game's script calls it in 7 places, among them feast_main_live_fowl.0001 (event), feast_main_live_fowl.9000 (event) and feast_main_stable_breakin.0001 (event). Patch 1.20.1.2, from game/common/scripted_triggers/00_feast_activity_triggers.txt.
What it checks
- Is available (not imprisoned)
• 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 (7 lines of game script)
feast_default_participant_including_player_trigger = {
is_available_quick = {
alive = yes
imprisoned = no
}
this != root
}As written in game/common/scripted_triggers/00_feast_activity_triggers.txt.
Where it is used
Every place in common/, events/ and history/ that calls feast_default_participant_including_player_trigger.
Source: game/common/scripted_triggers/00_feast_activity_triggers.txt and every file of common/, events/ and history/ that calls it, Crusader Kings III 1.20.1.2.