Wiki

trigger · has_stability

Definition

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

Description

check value of stability 0-1: Example has_stability < 0.6

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_stability is commonly used in political events or national focus branches to trigger different outcomes based on a nation's stability level—for example, firing unrest events when stability is low or unlocking specific focus options when stability is high. It is also frequently used in available blocks to restrict certain decisions so they can only be activated when stability meets the threshold.

# Example: Trigger internal unrest event when stability falls below 0.5
country_event = {
    id = my_mod.1
    trigger = {
        has_stability < 0.5
        NOT = { has_country_flag = unrest_event_fired }
    }
    ...
}

Synergy

  • [add_stability](/wiki/effect/add_stability): The most direct complementary effect. After detecting insufficient stability, immediately apply adjustments via this effect to create a complete "check → modify" logic chain.
  • [has_war_support](/wiki/trigger/has_war_support) (Note: similar numeric trigger with identical syntax) → corresponding [has_bombing_war_support](/wiki/trigger/has_bombing_war_support) in the actual list: Stability and war support are often designed to work together. Checking both simultaneously reflects overall domestic political health.
  • [add_political_power](/wiki/effect/add_political_power): Grant political power when stability reaches a threshold, commonly seen in conditional reward effect blocks after focus completion.
  • [has_country_flag](/wiki/trigger/has_country_flag): Pair with country flags to prevent duplicate event triggers within the same stability range—the standard companion for event deduplication.

Common Pitfalls

  1. Placing comparison operators after the trigger name rather than after the value: The correct syntax is has_stability < 0.6. Beginners often mistakenly write has_stability = { value < 0.6 }, which is invalid block syntax and causes script errors or conditions that never evaluate to true.
  2. Forgetting that numeric values range from 0–1, not percentages: The game UI displays percentages (e.g., 60%), but scripts must use decimals (0.6). Entering 60 directly will cause the condition to always be true (since the actual value is always less than 60).