trigger · resistance_speed

Hands-On Usage

resistance_speed is commonly used in mod scenarios related to occupation mechanics, such as determining whether a state's resistance growth rate is excessively high, thereby triggering additional suppression penalties or unlocking specific occupation policy options. A typical scenario involves filtering states with particularly rapid resistance spread within a limit block and automatically imposing stricter occupation laws or dynamic modifiers.

# When a state's resistance speed exceeds the threshold, apply additional suppression modifier to that state
every_controlled_state = {
    limit = {
        resistance_speed > 3
        has_active_resistance = yes
    }
    add_dynamic_modifier = {
        modifier = harsh_suppression_modifier
    }
}

Synergy

• [resistance](/wiki/trigger/resistance): Typically use resistance first to evaluate the absolute current resistance value, then use resistance_speed to assess growth trends. Combined, they enable more precise filtering of states that are "rapidly deteriorating."
• [has_active_resistance](/wiki/trigger/has_active_resistance): Resistance speed is only meaningful when active resistance exists. Pairing with this trigger avoids ineffective checks on states without resistance.
• [compliance](/wiki/trigger/compliance): Resistance speed and compliance are often inversely correlated. Using them together enables constructing dual-filter conditions of "low compliance + high resistance speed."
• [set_occupation_law](/wiki/effect/set_occupation_law): When resistance speed triggers an alarm, this effect is commonly used to automatically switch occupation laws to reduce subsequent growth rates, forming a complete condition-to-response logic chain.

Common Pitfalls

1. Confusing rate with current value: Beginners often reverse resistance_speed (resistance growth rate) and resistance (current resistance value), causing conditions to never trigger or logic to invert—the former measures weekly change amount, not absolute resistance levels.
2. Using outside STATE scope: resistance_speed is only valid in STATE scope. If placed directly in a country-scope trigger block without entering state scope via any_controlled_state / every_controlled_state, the script will error or fail silently.