trigger · is_in_peace_conference

Hands-On Usage

is_in_peace_conference is commonly used to restrict or unlock certain decisions/events during peace conferences, such as preventing players from triggering diplomatic decisions simultaneously at the negotiation table to avoid logical conflicts, or to display a dedicated notification event while the peace conference is ongoing. A typical scenario is placing it in the available block to ensure a decision can only be used when not in a peace conference state.

# A diplomatic decision that cannot be used during peace conferences
decision_my_diplomacy = {
    available = {
        NOT = { is_in_peace_conference = yes }
        has_political_power > 50
    }
    ...
}

# Or used in event trigger conditions, only fires during peace conferences
country_event = {
    trigger = {
        is_in_peace_conference = yes
        has_country_flag = my_special_war_flag
    }
    ...
}

Synergy

• [has_capitulated](/wiki/trigger/has_capitulated): Capitulation is typically the prerequisite for entering a peace conference. Combined with this trigger, you can precisely identify the special window period of "has capitulated and is still in peace negotiations."
• [has_defensive_war](/wiki/trigger/has_defensive_war): When used together with the defensive war state, you can distinguish between "passively taking damage and entering a peace conference" and "actively initiating warfare"—two completely different diplomatic situations.
• [any_enemy_country](/wiki/trigger/any_enemy_country): During peace conferences, you often need to iterate through current enemy countries to decide how to distribute war spoils. This trigger serves as an outer guard condition, preventing related logic from being accidentally triggered outside of peace conferences.
• [country_event](/wiki/effect/country_event): Trigger dedicated events at the boundary moments of peace conference start/end, using is_in_peace_conference as a conditional guard to ensure events only fire at the correct game phase.

Common Pitfalls

1. Writing yes as a specific number or omitting it: This trigger only accepts is_in_peace_conference = yes / = no syntax. It does not accept any numeric values or empty statements. Otherwise, script parsing will silently fail and the condition will never evaluate to true.
2. Mistakenly assuming scope can be a state or character: This trigger only works in COUNTRY scope. If written inside a limit but the outer scope has already switched to STATE or CHARACTER (for example, inside every_owned_state), you must first use owner = { is_in_peace_conference = yes } to jump back to country scope. Otherwise, the game will report a scope error or simply return false.