Wiki

trigger · pc_does_state_stack_dismantled

Definition

  • Supported scope:STATE
  • Supported target:none

Description

Checks if state got dismantled stacked on it in the peace conference.
Example:
FROM.FROM.FROM = { pc_does_state_stack_dismantled = yes }

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

Used in peace conference-related mods when you need to check whether a state has been stacked with "dismantled" status. Common scenarios include custom peace conference outcome events or decisions. The typical use case is to detect when the victor has applied a dismantlement operation to a state, then trigger subsequent resistance or compliance change logic.

# After peace conference ends, if the state is stacked with dismantled status, trigger a special event
peace_conference_on_state_taken = {
    FROM.FROM.FROM = {
        limit = {
            pc_does_state_stack_dismantled = yes
        }
        state_event = { id = my_mod.101 }
    }
}

Synergy

  • [pc_does_state_stack_demilitarized](/wiki/trigger/pc_does_state_stack_demilitarized): Part of the same peace conference state processing trigger series; commonly used together to distinguish whether a state was dismantled or demilitarized, allowing different downstream logic branches.
  • [has_state_flag](/wiki/trigger/has_state_flag): Can be used in combination to mark states after peace conference results are finalized, preventing duplicate event triggers on the same state.
  • [add_resistance](/wiki/effect/add_resistance): When a state is dismantled, it typically comes with high resistance; once the condition is confirmed true, you can directly adjust the state's resistance value.
  • [is_owned_by](/wiki/trigger/is_owned_by): Used to further restrict the current owner of the state, avoiding accidental triggers on non-target states.

Common Pitfalls

  1. Wrong Scope: This trigger must be called within STATE scope. Writing it directly in a country scope trigger block will silently fail or error out. You must chain through FROM.FROM.FROM = { } or similar constructs to switch to the correct state scope first.
  2. Timing Misjudgment: This trigger only has meaningful effect during the peace conference phase/settlement stage. If used in the available block of routine events or decisions, the condition will almost always be false, because the peace conference stacked statuses are cleared once the conference ends.