trigger · is_staging_coup

Hands-On Usage

is_staging_coup is commonly used to prevent certain diplomatic or intelligence decisions from triggering while your country is already staging a coup, avoiding logical conflicts. For example, in custom intelligence mods, you can use it to lock the "stage another coup" decision, ensuring only one target can be acted upon at a time.

# available block of a certain intelligence decision — prevent triggering another coup while one is already planned for this country
available = {
    NOT = { is_staging_coup = yes }
    has_country_flag = intelligence_network_ready
}

Synergy

• [has_civil_war](/wiki/trigger/has_civil_war): A successful coup often triggers civil war; the two are frequently combined in the same trigger block to determine whether the situation has already "entered hot conflict phase," thus preventing duplicate operations.
• [civilwar_target](/wiki/trigger/civilwar_target): Used to further confirm which country is the target of the current country's coup; used together with is_staging_coup, it can form the precise judgment of "staging a coup against country X."
• [has_country_flag](/wiki/trigger/has_country_flag): Commonly used alongside custom flags, setting/checking markers at various stages of the coup process; is_staging_coup serves as a double-check confirmation of the game's native state.
• [any_operative_leader](/wiki/trigger/any_operative_leader): Coup operations rely on operatives; frequently combined with this trigger to ensure the country has available operative resources before attempting a coup.

Common Pitfalls

1. Mistakenly assuming target parameter support: This trigger does not accept any target parameters (target is none); you can only write is_staging_coup = yes, not forms like is_staging_coup = GER, otherwise it will cause parsing errors or silent failures.
2. Scope confusion: This trigger can only be used within COUNTRY scope; if written in STATE or CHARACTER scope (such as operand scope blocks in certain operative events), the condition will silently return false, causing the logic to never be satisfied and making it easy to overlook during debugging.