Wiki

trigger · ideology_support_trigger

Definition

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

Description

Checks if the current scope has the specified ideology above the specified amount.
Usage: <Ideology> < <float>
Supported Ideologies: democratic, communism, fascism, neutrality.

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

ideology_support_trigger is commonly used to check whether a country's current ideology support rate meets a threshold, thereby determining whether a decision is available, an event should fire, or a national focus path should unlock. For example, in political mods, you can design conditions such as "allow a coup only if fascism support exceeds 50%".

available = {
    ideology_support_trigger = {
        fascism > 0.5
    }
}

Synergy

  • [has_country_leader_ideology](/wiki/trigger/has_country_leader_ideology) — Typically used in conjunction with this trigger to verify both the popular ideology support rate and the current leader's ideology, creating a comprehensive political state assessment.
  • [add_popularity](/wiki/effect/add_popularity) — Used alongside in effect blocks; when support falls short of the threshold, add popularity through events or decisions so subsequent trigger conditions are gradually satisfied.
  • [has_country_flag](/wiki/trigger/has_country_flag) — Often serves as a gating flag to prevent the same political narrative from repeatedly firing due to fluctuating support rates.
  • [add_political_power](/wiki/effect/add_political_power) — Awards political power after support rates meet conditions, creating a mechanic loop where "stronger popular support yields more governing resources".

Common Pitfalls

  1. Comparison operator reversed or mistyped — The official syntax is <Ideology> < <float> (meaning support rate greater than the specified value), but it's easy to accidentally write > or confuse the direction, causing the condition to never be satisfied or always be true. Always verify operator direction against the official definition.
  2. Confusion over value range concept — Support rates are floats between 0.0–1.0, but beginners often mistakenly enter percentage integers (such as 50 instead of 0.5), causing completely incorrect condition logic that won't error but will silently fail.