Wiki

trigger · compare_autonomy_state

Definition

  • Supported scope:COUNTRY
  • Supported target:none

Description

check if autonomy state is higher than other one, example:
compare_autonomy_state > puppet

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

compare_autonomy_state is commonly used in autonomy-related decisions or national focuses to check whether the autonomy level between a overlord and its subject meets a certain threshold, thereby unlocking specific options or triggering scripted events. For example, in a subject independence mod, the overlord is only allowed to take certain restrictive decisions after the subject's autonomy tier has risen above puppet:

available = {
    compare_autonomy_state > puppet
}

Synergy

  • [has_autonomy_state](/wiki/trigger/has_autonomy_state): Use has_autonomy_state first to match the exact current autonomy state, then use this trigger for range comparison. Together they construct fine-grained "within a range" logic.
  • [add_autonomy_score](/wiki/effect/add_autonomy_score): Use together in effect blocks; when the comparison evaluates to true, trigger increases or decreases to autonomy score, implementing the logic of phased autonomy progression.
  • [compare_autonomy_progress_ratio](/wiki/trigger/compare_autonomy_progress_ratio): Use in conjunction with this trigger—one judges the autonomy tier level, the other judges the progress ratio within the current tier, allowing you to write more precise conditional layers.
  • [end_puppet](/wiki/effect/end_puppet): Trigger the removal of subject status when autonomy tier has risen above a specific state. Use this trigger as a precondition to avoid prematurely ending the subject relationship.

Common Pitfalls

  1. Case sensitivity and autonomy tier name spelling errors: The identifiers for autonomy tiers (such as puppet, dominion, autonomous_puppet, etc.) must match exactly as defined in-game. Spelling or case errors will cause the condition to never fire, and typically produce no obvious error message.
  2. Misusing scope: This trigger is only valid in COUNTRY scope. If placed in STATE or CHARACTER scope it will not error but always evaluate to false. Beginners often mistakenly place it inside regional loops like any_owned_state, causing the logic to fail.