Wiki

trigger · is_owned_and_controlled_by

Definition

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

Description

check if state is owned by

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_owned_and_controlled_by is commonly used in resistance movements, occupation laws, compliance systems, and other condition checks to ensure a state is both owned and controlled by the target country (not merely occupied). For example, in decisions or events, you can check whether the player has completely secured control of a strategic state:

# available block in a decision: only executable when you fully control the state
available = {
    42 = {  # some state ID
        is_owned_and_controlled_by = ROOT
    }
}

Synergy

  • [is_owned_by](/wiki/trigger/is_owned_by): Use when you only need to check sovereignty without caring about actual control. It complements this trigger by helping distinguish between "nominal ownership" and "actual control" scenarios.
  • [is_controlled_by](/wiki/trigger/is_controlled_by): When used together, you can separately refine "control without ownership" occupation states. Often paired with this trigger in if/else branches during resistance events.
  • [set_occupation_law](/wiki/effect/set_occupation_law): Set occupation laws only after confirming a state is fully owned and controlled, avoiding incorrect policy application to states that aren't yet securely held.
  • [compliance](/wiki/trigger/compliance): Frequently placed alongside this trigger in limit blocks to ensure compliance checks apply only to states you truly control.

Common Pitfalls

  1. Confusing "ownership" with "control": Beginners often assume occupation of an enemy state triggers the condition, but this trigger requires both ownership and control to be satisfied simultaneously. Mere military occupation (controller ≠ owner) returns false; use is_controlled_by instead for occupation scenarios.
  2. Incorrect scope placement: This trigger must be called under STATE scope. Placing it directly at the top level of a country scope event trigger block causes errors. You must first switch to the corresponding state scope using state IDs or capital_scope before using it.