trigger · `compliance_speed`

Definition

Supported scope:STATE
Supported target:any

Description

Compares the current compliance speed of a state to a value. Example: compliance_speed > 50

实战 · 配合 · 坑

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

实战用法

compliance_speed 常用于占领系统相关的 mod 中，例如根据当前顺从度增长速率动态解锁决策或切换占领法令——比如当某地区顺从度增长过慢时，自动触发惩罚性事件或限制建设选项。它也适合用于 AI 逻辑判断中，当顺从度增速达到阈值时才允许投入资源进行基础设施建设。

# 仅当该州顺从度增长速度足够高时，才允许激活该决策
available = {
    compliance_speed > 10
    compliance > 50
}

配合关系

[compliance](/wiki/trigger/compliance)：两者几乎总是成对出现，compliance 判断当前绝对值，compliance_speed 判断增长趋势，组合使用可以更精确地描述占领状态。
[resistance_speed](/wiki/trigger/resistance_speed)：顺从度速度与抵抗速度互为镜像，同时检查两者可以判断局势是否真正趋于稳定，而非仅靠单一指标误判。
[occupation_law](/wiki/trigger/occupation_law)：当前占领法令直接影响顺从度增速，结合使用可以构建"当法令为 X 且增速不足时触发补救逻辑"的完整条件链。
[set_occupation_law](/wiki/effect/set_occupation_law)：常作为上述判断的后续 effect，在顺从度增速不达标时自动切换更宽松的占领法令以加速增长。

常见坑

误将其当作顺从度绝对值使用：compliance_speed 比较的是每日/每周的增长速率，而非顺从度本身的数值；想判断顺从度是否已经高于某个数字，应使用 compliance，否则逻辑会完全错误。
忽略负值情况：顺从度增速可以为负数（即顺从度正在下降），条件如 compliance_speed > 0 才能真正区分"正在增长"与"正在下降"，新手常只写正数阈值而漏掉对负增速的处理，导致决策在顺从度崩溃时仍然可用。

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

compliance_speed is commonly used in occupation system-related mods, such as dynamically unlocking decisions or switching occupation laws based on the current compliance growth rate——for example, when a region's compliance growth is too slow, automatically trigger punitive events or restrict construction options. It's also suitable for AI logic judgments, allowing resource allocation to infrastructure construction only when compliance growth speed reaches a threshold.

# Only allow activating this decision when the state's compliance growth speed is high enough
available = {
    compliance_speed > 10
    compliance > 50
}

Synergy

[compliance](/wiki/trigger/compliance): The two almost always appear in pairs; compliance checks the current absolute value, while compliance_speed checks the growth trend. Combined use enables more precise description of occupation status.
[resistance_speed](/wiki/trigger/resistance_speed): Compliance speed and resistance speed are mirror images of each other. Checking both simultaneously allows you to determine if the situation is truly stabilizing, rather than misjudging based on a single metric.
[occupation_law](/wiki/trigger/occupation_law): The current occupation law directly affects compliance growth speed. Combined use enables building complete conditional chains like "trigger remedial logic when law is X and growth speed is insufficient."
[set_occupation_law](/wiki/effect/set_occupation_law): Commonly serves as the consequent effect to the above judgments, automatically switching to a more lenient occupation law when compliance growth speed falls short.

Common Pitfalls

Mistaking it for absolute compliance value: compliance_speed compares the growth rate per day/week, not the compliance value itself; to check whether compliance has already exceeded a certain number, use compliance instead, otherwise the logic will be completely wrong.
Overlooking negative values: Compliance growth speed can be negative (meaning compliance is decreasing). Conditions like compliance_speed > 0 are necessary to truly distinguish between "currently increasing" and "currently decreasing." Beginners often only set positive thresholds while missing handling for negative growth speeds, causing decisions to remain available even when compliance collapses.

trigger · compliance_speed