Hands-On Usage
This trigger is commonly used in mods related to peace conferences. Use it when you want to restrict certain decisions or events to fire only on states within the "sphere of influence that the victor can actually claim." For example, in custom peace conference logic, you can use it to filter out states that the victor cannot legitimately claim due to distance or sphere-of-influence restrictions, preventing invalid territorial distributions.
# In the trigger block of peace conference-related events, exclude states outside the sphere of influence
peace_conference_peace_options = {
limit = {
NOT = {
pc_is_state_outside_influence_for_winner = ROOT
}
is_owned_by = FROM
}
}
Synergy
[pc_is_state_claimed_by](/wiki/trigger/pc_is_state_claimed_by) — Typically used in conjunction with this trigger. First check whether the state is claimed by a faction, then use this trigger to confirm whether that claim falls within the victor's effective sphere of influence. This dual filtering ensures territorial distribution logic remains lawful.
[pc_is_state_claimed](/wiki/trigger/pc_is_state_claimed) — Used to check whether the state has any claimants. Combined with this trigger, you can construct logic branches like "has a claim but is outside the range, so skip."
[is_owned_by](/wiki/trigger/is_owned_by) — Use together to confirm the current ownership of the state, ensuring the judgment target is land controlled by a belligerent party, not already belonging to the victor.
[any_neighbor_state](/wiki/trigger/any_neighbor_state) — Can be nested within this trigger in adjacent state iteration scenarios to batch-check whether all surrounding states are completely outside the sphere of influence, assisting in constructing contiguous territory judgments.
Common Pitfalls
- Wrong scope usage: This trigger must be called under
STATE scope. If written in a country scope (such as in an event's immediate block or a country-level trigger block), it will silently fail or throw an error. You must first switch to state scope using any_state/every_state or similar, then use this trigger.
- Target syntax confusion: The parameter receives the victor's TAG or a valid target (such as
ROOT, FROM), not the state being checked itself — the state is implicitly determined by the current scope. Beginners often mistakenly fill in the state's TAG or OWNER in the parameter position, resulting in completely incorrect logic judgment.