Wiki

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

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

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