trigger · `is_high_command`

Definition

Supported scope:CHARACTER
Supported target:none

Description

_is_high_command_ = yes/no - Checks if the character in scope is hired as high command

实战 · 配合 · 坑

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

实战用法

is_high_command 常用于检测某个角色当前是否以"高级指挥官"顾问身份被雇用，适合在解锁特殊决议、触发事件或限制特定操作时作为前置条件。例如，若你想在某位将领担任高级指挥官期间才允许执行某项军事决策，可以这样写：

available = {
    any_character = {
        is_high_command = yes
        has_trait = trait_brilliant_strategist
    }
}

配合关系

[is_hired_as_advisor](/wiki/trigger/is_hired_as_advisor)：两者同为顾问状态检查，is_high_command 专门区分高级指挥官职位，与 is_hired_as_advisor 组合可精确区分角色的顾问类型，避免误判。
[has_advisor_role](/wiki/trigger/has_advisor_role)：可进一步核查角色具体持有的顾问角色槽，与 is_high_command 配合使用能做双重验证，适合多职位角色并存的复杂 mod。
[remove_advisor_role](/wiki/effect/remove_advisor_role)：当条件满足（角色确实是高级指挥官）后，可通过此 effect 移除其角色，实现"先判断再操作"的标准流程。
[has_trait](/wiki/trigger/has_trait)：高级指挥官通常需要特定 trait 才有意义，两者搭配可对角色能力做组合筛选。

常见坑

Scope 错误：is_high_command 必须在 CHARACTER scope 下使用，直接写在国家 scope（如 country_event 的顶层 trigger 块）中会静默失败或报错，需先通过 any_character、every_character 等方式切入角色 scope。
与 is_advisor 混淆：is_advisor 只检查角色是否以任意顾问身份在职，而 is_high_command 专指高级指挥官职位；若需精确匹配职位类型，两者不可互换使用。

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

is_high_command is commonly used to check whether a character is currently employed as a "High Command" advisor, making it ideal as a prerequisite condition for unlocking special decisions, triggering events, or restricting specific operations. For example, if you want to allow a particular military decision to execute only while a general serves as a high command advisor, you can write:

available = {
    any_character = {
        is_high_command = yes
        has_trait = trait_brilliant_strategist
    }
}

Synergy

[is_hired_as_advisor](/wiki/trigger/is_hired_as_advisor): Both serve as advisor status checks. is_high_command specifically distinguishes the High Command position, while combining it with is_hired_as_advisor allows precise differentiation of a character's advisor type and prevents misidentification.
[has_advisor_role](/wiki/trigger/has_advisor_role): Further verifies the specific advisor role slot a character holds. Using it alongside is_high_command enables dual validation, ideal for complex mods with multiple concurrent character roles.
[remove_advisor_role](/wiki/effect/remove_advisor_role): Once the condition is met (the character is indeed a high command advisor), this effect can remove their role, implementing a standard "check then act" workflow.
[has_trait](/wiki/trigger/has_trait): High command advisors typically require specific traits to be meaningful. Pairing these two allows composite filtering of character capabilities.

Common Pitfalls

Scope Mismatch: is_high_command must be used within a CHARACTER scope. Placing it directly in a country scope (such as at the top level of a country_event's trigger block) will silently fail or produce errors. You must first enter character scope via any_character, every_character, or similar constructs.
Confusion with is_advisor: is_advisor only checks whether a character is employed in any advisor capacity, while is_high_command specifically refers to the High Command position. If precise position matching is required, these two cannot be used interchangeably.

trigger · is_high_command