effect · add_compliance

Hands-On Usage

add_compliance is commonly used in occupation events or decisions to reward player administrative actions—for example, increasing the compliance of an occupied state after completing infrastructure construction, or batch-adding compliance to all occupied states via a specific national focus. Below is a simple example of usage within a decision option:

option = {
    name = my_decision.opt_a
    # Adds compliance to the current STATE scope
    add_compliance = 15
}

Synergy

• [compliance](/wiki/trigger/compliance) — Use this trigger first to check if compliance reaches the threshold, then decide whether to trigger reward logic, avoiding wasted effects or unnecessary cascades.
• [set_occupation_law](/wiki/effect/set_occupation_law) — Compliance is closely tied to occupation law; it's common to adjust compliance synchronously after switching laws to simulate policy effects.
• [add_resistance](/wiki/effect/add_resistance) — Compliance and resistance have an inverse relationship; operating both simultaneously allows precise simulation of political stability in occupied territories.
• [add_state_modifier](/wiki/effect/add_state_modifier) — Pair with custom modifiers to add production or manpower bonuses to high-compliance states, implementing a "high compliance = more output" design logic.

Common Pitfalls

1. Incorrect Scope: add_compliance must execute within a STATE scope. Beginners often call it directly under COUNTRY scope, causing script errors or silent failure; the correct approach is to switch to state scope first using every_state / capital_scope or similar, then call the effect.
2. Confusion with set_compliance: add_compliance is incremental stacking, while set_compliance is direct assignment; misusing set_compliance in loops or event chains will overwrite all previous accumulation, while misusing add_compliance prevents resetting compliance to a specific baseline value.