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 }

实战 · 配合 · 坑

实战内容由 AI 生成,并已对照 vanilla 命令词表校验 —— 请当作起点而非权威依据。上方的定义节才是游戏自带文档原文。

实战用法

在和平会议相关的 mod 中,当需要判断某个州是否被叠加了"解体"(dismantled)处理时使用此 trigger,例如自定义和平会议结果事件或决议。常见场景是检测战胜方对某州施加了拆解操作后,触发后续的抵抗或合规变化逻辑。

# 和平会议结束后,若该州被叠加了解体,则触发特殊事件
peace_conference_on_state_taken = {
    FROM.FROM.FROM = {
        limit = {
            pc_does_state_stack_dismantled = yes
        }
        state_event = { id = my_mod.101 }
    }
}

配合关系

  • [pc_does_state_stack_demilitarized](/wiki/trigger/pc_does_state_stack_demilitarized):同属和平会议州处理系列 trigger,常一起用于区分州是被解体还是被非军事化,从而走不同的后续逻辑分支。
  • [has_state_flag](/wiki/trigger/has_state_flag):配合使用可在和平会议结果确定后打标记,防止同一州的事件重复触发。
  • [add_resistance](/wiki/effect/add_resistance):当州被解体时往往伴随高抵抗,判断条件成立后可直接调整该州的抵抗值。
  • [is_owned_by](/wiki/trigger/is_owned_by):用于进一步限定该州的当前归属国,避免对非目标国的州误触发。

常见坑

  1. Scope 用错:此 trigger 必须在 STATE scope 下调用,直接写在国家 scope 的 trigger 块中会静默失败或报错,务必通过 FROM.FROM.FROM = { } 等链式跳转先切换到正确的州 scope。
  2. 时机误判:该 trigger 仅在和平会议期间/结算阶段有意义,若在日常事件或决议的 available 块中使用,条件往往永远为假,因为和平会议的叠加状态在会议结束后会被清除。

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.