trigger · `intel_level_over`

Definition

Supported scope:COUNTRY
Supported target:THIS, ROOT, PREV, FROM, OWNER, CONTROLLER, OCCUPIED, CAPITAL

Description

Compare the absolute, percentage based, intel level the scoped country has over
the specified one:
GER = {
  # is true if all predicates are satisfied
  intel_level_over = { 
    target = POL
    civilian_intel > 0.5  # GER has more than 50% civ. intel over POL
    army_intel = 0  # GER has no army intel over POL
    navy_intel > 0  # GER has at least some navy intel over POL
    # airforce_intel is not specified and thus ignored in the comparison

    # NOTE: since we are comparing the intel level of a country over another,
    # checking for values less than 0 does not make sense
    # NOTE: since we are comparing percentages, using values greater than 1
    # does not make sense.
  }
}

实战 · 配合 · 坑

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

实战用法

intel_level_over 常见于谍报系统相关的 mod 场景，例如当一国对目标国的情报渗透达到一定程度后才解锁特殊决策、外交选项或特工行动。比如你想实现"只有当德国对波兰的民事情报超过 50% 时才能触发某个间谍事件"的逻辑，就可以用它作为 available 或 trigger 块的前置条件。

# 示例：德国对法国拥有足够情报时才允许某决策
decision_example = {
    available = {
        tag = GER
        intel_level_over = {
            target = FRA
            civilian_intel > 0.5
            army_intel > 0.3
        }
    }
    # ...
}

配合关系

[has_collaboration](/wiki/trigger/has_collaboration)：情报渗透通常与协作度并行推进，可以同时检查目标国的协作度，确保情报与政治渗透双线满足才触发效果。
[compare_intel_with](/wiki/trigger/compare_intel_with)：当需要在两国情报水平之间做相对比较（而非绝对百分比）时与本 trigger 互补使用，覆盖不同维度的情报判断需求。
[add_intel](/wiki/effect/add_intel)：通常作为满足本 trigger 条件后的奖励或推进手段，在效果块中继续拉高对目标的情报值，形成"达到阈值→触发→再提升"的逻辑链。
[has_captured_operative](/wiki/trigger/has_captured_operative)：抓获特工往往是情报博弈的结果，可与 intel_level_over 组合，检查"既渗透充分又抓到对方特工"时才解锁更高级的行动。

常见坑

数值范围误解：intel_level_over 比较的是百分比（0 到 1 之间），新手容易写成 civilian_intel > 50 这样的整数形式，导致条件永远无法满足，因为实际数值不会超过 1。
对未指定字段的误判：没有写出的情报类型（如未写 airforce_intel）会被完全忽略而非默认视为 0，新手容易误以为不写就等于"要求该项为 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

intel_level_over is commonly used in intelligence system-related mod scenarios, such as unlocking special decisions, diplomatic options, or operative actions only after a nation achieves sufficient intelligence penetration into a target country. For example, if you want to implement logic like "trigger a specific spy event only when Germany's civilian intelligence on Poland exceeds 50%", you can use it as a prerequisite condition in an available or trigger block.

# Example: Allow a decision only when Germany has sufficient intelligence on France
decision_example = {
    available = {
        tag = GER
        intel_level_over = {
            target = FRA
            civilian_intel > 0.5
            army_intel > 0.3
        }
    }
    # ...
}

Synergy

[has_collaboration](/wiki/trigger/has_collaboration): Intelligence penetration typically progresses in parallel with collaboration levels. You can check the target nation's collaboration simultaneously to ensure both intelligence and political penetration thresholds are met before triggering effects.
[compare_intel_with](/wiki/trigger/compare_intel_with): Complements this trigger when you need to make relative comparisons between two nations' intelligence levels (rather than absolute percentages), covering different dimensions of intelligence assessment.
[add_intel](/wiki/effect/add_intel): Usually serves as a reward or advancement mechanism after this trigger's conditions are satisfied, further increasing intelligence values on the target within the effect block, forming a "reach threshold → trigger → further enhance" logic chain.
[has_captured_operative](/wiki/trigger/has_captured_operative): Capturing operatives is often the outcome of intelligence warfare. You can combine it with intel_level_over to unlock more advanced actions only when conditions like "sufficient penetration AND captured enemy operative" are met.

Common Pitfalls

Misunderstanding value ranges: intel_level_over compares percentages (between 0 and 1). Beginners often write civilian_intel > 50 in integer form, causing the condition to never be satisfied because actual values never exceed 1.
Misinterpreting unspecified fields: Intelligence types that are not written out (such as omitting airforce_intel) are completely ignored rather than defaulting to 0. Beginners often mistakenly believe that not writing a field means "require that field to be 0", causing them to overlook intelligence dimensions that should be constrained. It's recommended to explicitly write out all fields you need to restrict.

trigger · intel_level_over