Wiki

trigger · has_full_control_of_state

Definition

  • Supported scope:COUNTRY
  • Supported target:THIS, ROOT, PREV, FROM, CAPITAL

Description

check controller for state(s)

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

has_full_control_of_state is commonly used to determine whether a player or AI nation maintains complete control over a state (i.e., controller and owner are identical with zero resistance). It is well-suited for restricting trigger conditions in decisions, national focuses, or mission availability checks. For example, you can restrict a specific construction bonus event or unlock an option to only trigger when your nation completely controls a critical industrial state.

# This decision is only available when fully controlling STATE_42 (Île-de-France)
available = {
    has_full_control_of_state = 42
}

Synergy

  • [controls_state](/wiki/trigger/controls_state): controls_state only checks whether a state is controlled (without requiring full control). Used alongside has_full_control_of_state, it allows you to distinguish between "nominal occupation" and "firm control" in branching logic, granting different rewards accordingly.
  • [any_controlled_state](/wiki/trigger/any_controlled_state): Iterates through all controlled states and nests has_full_control_of_state as a sub-condition, enabling verification of whether at least one fully-controlled state exists within a given region.
  • [add_state_core](/wiki/effect/add_state_core): Commonly triggered as an effect after has_full_control_of_state is satisfied, coring the fully-controlled state to reinforce the narrative logic of "declaring sovereignty after consolidating occupation."
  • [all_controlled_state](/wiki/trigger/all_controlled_state): Combined with has_full_control_of_state, it validates whether all controlled states achieve full control status, useful for determining whether a war theater has been completely secured.

Common Pitfalls

  1. Confusing "control" with "full control": Newcomers often mistakenly substitute controls_state for this trigger, but the former returns true even if enemy militia or resistance remains in the state, making the condition much looser than intended. Always choose explicitly based on your actual requirements.
  2. Incorrect scope direction: This trigger's scope is COUNTRY and must be used within a country scope context. If written inside a STATE scope block (such as within a sub-block of every_owned_state) without switching back to country scope, the script will error or silently fail.