trigger · `pc_is_state_claimed_and_taken_by`

Definition

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

Description

Check if state is claimed with a take_states action in conference for TAG
Example:
pc_is_state_claimed_and_taken_by = SOV/ROOT/ROOT.FROM

实战 · 配合 · 坑

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

实战用法

此 trigger 常用于和平会议相关的 mod 场景，例如在会议结束后的事件或决议中，检测某个国家是否通过 take_states 动作声索并夺取了特定州，从而触发后续剧情分支或惩罚机制。典型场景包括：战后重建决议的解锁条件、或当某大国在会议中吞并关键州后自动激活某些区域事件。

# 在某个 STATE scope 的事件触发中判断苏联是否通过会议取得了该州
some_state_event = {
    trigger = {
        pc_is_state_claimed_and_taken_by = SOV
    }
    # ...
}

# 也可以用动态 scope 写法
pc_is_state_claimed_and_taken_by = ROOT.FROM

配合关系

[pc_is_state_claimed_by](/wiki/trigger/pc_is_state_claimed_by)：先用此 trigger 检查该州是否被某国在会议中提出声索，再用 pc_is_state_claimed_and_taken_by 进一步确认是否真正通过 take_states 取得，形成两层判断逻辑。
[is_owned_by](/wiki/trigger/is_owned_by)：会议结束后配合使用，验证该州是否在游戏状态层面也确实已归属目标国，避免会议数据与实际所有权不同步时产生逻辑漏洞。
[has_state_flag](/wiki/trigger/has_state_flag)：常用于标记"该州已被会议瓜分"这一状态，与 pc_is_state_claimed_and_taken_by 组合构成条件门控，防止事件重复触发。
[set_state_owner_to](/wiki/effect/set_state_owner_to)：在确认会议声索成立后，作为 effect 执行实际的所有权转移，是此 trigger 最直接的后续动作。

常见坑

scope 混用：此 trigger 必须在 STATE scope 下使用，新手常在 COUNTRY scope 的事件或决议 trigger 块中直接写，导致解析报错或静默失效；需要先通过 any_state / every_state 等进入正确 scope。
会议数据生命周期误解：和平会议结束后，会议相关的内部数据可能已被清除，此 trigger 在会议进行中最为可靠；若在会议结束很久后的事件中调用，可能始终返回 false，应配合 [has_state_flag](/wiki/trigger/has_state_flag) 在会议期间预先打好标记来规避此问题。

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

This trigger is commonly used in mod scenarios related to peace conferences. For example, in events or decisions that occur after a conference concludes, you can check whether a specific country has claimed and seized a particular state through the take_states action, thereby triggering subsequent story branches or penalty mechanics. Typical use cases include: unlocking conditions for post-war reconstruction decisions, or automatically activating regional events when a major power annexes key states during a conference.

# Check whether the Soviet Union obtained this state through a peace conference in a STATE scope event trigger
some_state_event = {
    trigger = {
        pc_is_state_claimed_and_taken_by = SOV
    }
    # ...
}

# Can also use dynamic scope syntax
pc_is_state_claimed_and_taken_by = ROOT.FROM

Synergy

[pc_is_state_claimed_by](/wiki/trigger/pc_is_state_claimed_by): First use this trigger to check whether a state has been claimed by a country during a conference, then use pc_is_state_claimed_and_taken_by to further confirm whether it was actually obtained through take_states, creating a two-layer verification logic.
[is_owned_by](/wiki/trigger/is_owned_by): Use together after the conference concludes to verify that the state is indeed owned by the target country at the game state level, preventing logic gaps when conference data and actual ownership become desynchronized.
[has_state_flag](/wiki/trigger/has_state_flag): Commonly used to mark the state as "already partitioned in the conference," combined with pc_is_state_claimed_and_taken_by to form conditional gating and prevent event duplication.
[set_state_owner_to](/wiki/effect/set_state_owner_to): After confirming that the conference claim is valid, execute the actual ownership transfer as an effect. This is the most direct follow-up action to this trigger.

Common Pitfalls

Scope confusion: This trigger must be used within a STATE scope. Beginners often write it directly in the trigger block of events or decisions within a COUNTRY scope, causing parsing errors or silent failures. You must first enter the correct scope through any_state / every_state or similar constructs.
Misunderstanding of peace conference data lifecycle: After a peace conference concludes, the internal conference data may be cleared. This trigger is most reliable during the conference itself. If called in an event long after the conference ends, it may always return false. Mitigate this by using [has_state_flag](/wiki/trigger/has_state_flag) to set flags during the conference period in advance.

trigger · pc_is_state_claimed_and_taken_by