trigger · `all_operative_leader`

Definition

Supported scope:COUNTRY, OPERATION
Supported target:none

Description

check if all operatives meets the trigger. tooltip=key can be defined to override title

实战 · 配合 · 坑

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

实战用法

all_operative_leader 常用于检查某国所有情报人员是否同时满足特定条件，例如在决议或事件中判断全体特工是否均已具备某项特质、达到某个技能层级，或处于某种任务状态，从而决定是否解锁奖励或触发剧情。典型场景包括：特工培训计划完成判定、精英特工组织成就达成等。

# 判断该国所有特工均拥有 operative_trait_tough 特质才允许决议完成
available = {
    all_operative_leader = {
        has_trait = operative_trait_tough
    }
}

配合关系

has_trait — 最常嵌套在 all_operative_leader 内部，用于检查每名特工是否都持有指定特质，是该 trigger 最核心的内层条件。
operative_leader_mission — 可在内部检查所有特工当前执行的任务类型，用于判断全部特工是否都处于待命或同一任务状态。
is_operative_captured — 在内部检查特工是否被俘，常用于"确保无一特工落网"类的条件判断。
skill — 嵌套于内部检查特工的技能数值，用于判定全体特工是否均达到精英级别的门槛。

常见坑

scope 混淆：all_operative_leader 只能在 COUNTRY 或 OPERATION scope 下使用，新手容易误将其写在 UNIT_LEADER 或 CHARACTER scope 的条件块内，导致脚本报错或静默失效；请确认外层 scope 正确。
与 any_operative_leader 语义混淆：all_operative_leader 要求全部特工满足条件（逻辑"与"），而 any_operative_leader 只需至少一名满足即可（逻辑"或"）；误用会导致条件比预期严苛或宽松得多，且不会触发明显报错，极难排查。

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

all_operative_leader is commonly used to check whether all operatives belonging to a country simultaneously meet specific conditions — for example, verifying in a decision or event that every operative possesses a certain trait, has reached a particular skill threshold, or is in a given mission state, in order to determine whether a reward should be unlocked or a story beat triggered. Typical use cases include: completion checks for operative training programs, and achievement conditions for elite intelligence organizations.

# Only allow the decision to complete if every operative in the country has the operative_trait_tough trait
available = {
    all_operative_leader = {
        has_trait = operative_trait_tough
    }
}

Synergy

has_trait — Most frequently nested inside all_operative_leader to check whether each operative holds a specified trait; this is the most essential inner condition for this trigger.
operative_leader_mission — Can be used inside to check the current mission type of all operatives, useful for determining whether every operative is on standby or assigned to the same mission.
is_operative_captured — Used inside to check whether an operative has been captured; commonly employed in conditions such as "ensure no operative has been caught."
skill — Nested inside to check an operative's skill value, used to determine whether all operatives have reached an elite-level threshold.

Common Pitfalls

Scope confusion: all_operative_leader can only be used within a COUNTRY or OPERATION scope. Beginners often mistakenly place it inside a condition block scoped to UNIT_LEADER or CHARACTER, causing script errors or silent failures. Always verify that the enclosing scope is correct.
Semantic confusion with any_operative_leader: all_operative_leader requires every operative to satisfy the condition (logical AND), whereas any_operative_leader only requires at least one to do so (logical OR). Mixing them up will make your condition far stricter or more lenient than intended, and since no obvious error is thrown, this kind of bug is extremely difficult to track down.

trigger · all_operative_leader