trigger · has_occupation_modifier

Hands-On Usage

has_occupation_modifier is commonly used in mods related to the occupation system, such as deciding whether to trigger specific events, activate decisions, or restrict certain actions based on the existence of a particular occupation modifier. Typical scenarios include: allowing resistance-related decision chains to execute or unlocking additional compliance bonuses only when the occupying country has applied a specific modifier to the state.

# Only trigger resistance events when the state has a specific occupation modifier
state_event = {
    id = resistance_flavor.1
    trigger = {
        has_occupation_modifier = brutal_occupation_modifier
    }
}

Synergy

• [has_active_resistance](/wiki/trigger/has_active_resistance): Frequently used together with has_occupation_modifier to confirm the presence of an occupation modifier while further checking whether the state has active resistance, narrowing the trigger scope with dual conditions.
• [compliance](/wiki/trigger/compliance): Occupation modifiers often affect compliance threshold evaluations; combining them enables fine-grained logic such as "only trigger when a specific modifier is present and compliance is below a certain value."
• [add_state_modifier](/wiki/effect/add_state_modifier): After trigger conditions are met, use effect blocks to stack new state modifiers, enabling cascading upgrade designs for occupation modifier chains.
• [occupation_law](/wiki/trigger/occupation_law): Occupation laws and occupation modifiers frequently work together to define the complete state of an occupation policy; pairing them allows precise descriptions of the current occupation environment.

Common Pitfalls

1. Modifier name typos causing permanent falsehood: The value of has_occupation_modifier must exactly match the modifier name in the occupation_modifier definition file (case-sensitive). Misspelling the name will not produce an error but will cause the condition to always return false, making it extremely difficult to debug.
2. Using in non-STATE scopes: This trigger only works in STATE scope. If mistakenly placed in trigger blocks within COUNTRY or CHARACTER scopes, the game typically silently ignores it or reports a scope error. Beginners often accidentally place it in the wrong location due to scope nesting confusion.