trigger · `resistance_speed`

Definition

Supported scope:STATE
Supported target:any

Description

Compares the current resistance speed of a state to a value. Example: resistance_speed > 50

实战 · 配合 · 坑

实战内容由 AI 生成,并已对照 vanilla 命令词表校验 —— 请当作起点而非权威依据。上方的定义节才是游戏自带文档原文。

实战用法

resistance_speed 常用于占领机制相关的 mod 场景，例如判断某州的抵抗增长速度是否过高，从而触发额外的镇压惩罚或解锁特定的占领政策选项。典型场景是在 limit 块中筛选出抵抗蔓延特别快的州，自动施加更严苛的占领法或动态修正。

# 当某州抵抗速度超过阈值时，对该州施加额外镇压修正
every_controlled_state = {
    limit = {
        resistance_speed > 3
        has_active_resistance = yes
    }
    add_dynamic_modifier = {
        modifier = harsh_suppression_modifier
    }
}

配合关系

[resistance](/wiki/trigger/resistance)：通常先用 resistance 判断当前抵抗值绝对量，再用 resistance_speed 判断增长趋势，两者结合能更精准地筛选"正在快速恶化"的州。
[has_active_resistance](/wiki/trigger/has_active_resistance)：抵抗速度只在存在活跃抵抗时有意义，配合此 trigger 可避免对无抵抗州做无效判断。
[compliance](/wiki/trigger/compliance)：抵抗速度与顺从度往往负相关，组合使用可构建"低顺从 + 高抵抗速度"的双重筛选条件。
[set_occupation_law](/wiki/effect/set_occupation_law)：当抵抗速度触发警报后，常用此 effect 自动切换占领法以降低后续增长速率，形成条件→响应的完整逻辑链。

常见坑

混淆速度与当前值：新手容易把 resistance_speed（抵抗增长速度）与 resistance（当前抵抗值）用反，导致条件永远不触发或逻辑倒置——前者衡量的是每周变化量，而非抵抗的绝对高低。
在非 STATE scope 下使用：resistance_speed 仅在 STATE scope 下有效，若直接写在国家 scope 的 trigger 块中而不通过 any_controlled_state / every_controlled_state 等进入州 scope，脚本会报错或静默失效。

Hands-On Notes

Hands-on notes are AI-generated and checked against the vanilla command vocabulary — treat them as a starting point, not authoritative reference. The definition above is the game's own documentation.

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

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.
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.

trigger · resistance_speed