trigger · `pc_is_state_claimed`

Definition

Supported scope:STATE
Supported target:none

Description

Check if state is claimed (and uncontested) in conferenceExample:
pc_is_state_claimed = yes/no

实战 · 配合 · 坑

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

实战用法

pc_is_state_claimed 常用于和会议相关的 mod 场景，例如在战后和平会议或领土分配系统中，判断某个州是否已被某方认领且无争议，从而决定是否允许进一步的外交或建设行动。典型场景是在 available 块中限制某决议只有在当前州已被无争议认领时才能触发。

# 在一个针对 STATE scope 的 decision available 中使用
available = {
    pc_is_state_claimed = yes
    is_owned_by = ROOT
}

配合关系

[pc_is_state_claimed_by](/wiki/trigger/pc_is_state_claimed_by)：配合使用可以在确认州已被认领的前提下，进一步精确判断是由哪个国家认领，逻辑更严谨。
[has_contested_owner](/wiki/trigger/has_contested_owner)：pc_is_state_claimed 检查的是"无争议"认领，配合此 trigger 可以区分有争议与无争议状态，构建更完整的条件分支。
[is_owned_by](/wiki/trigger/is_owned_by)：认领与实际控制是两回事，通常需要同时确认州的所有权，避免逻辑漏洞。
[add_claim_by](/wiki/effect/add_claim_by)：在 effect 块中搭配使用，可在认领条件不满足时通过此 effect 补充认领，形成"检查→补救"的完整流程。

常见坑

混淆"认领"与"核心"：新手常将 pc_is_state_claimed 与 [is_core_of](/wiki/trigger/is_core_of) 混用，但前者专属于和会（Peace Conference）系统上下文，在非和会流程中使用可能始终返回假，而非期望的领土归属判断。
忽略"无争议"含义：此 trigger 要求认领是无争议的（uncontested），若该州同时被多方认领存在争议，结果为假。新手若只用它来判断"有没有人认领"而未考虑争议情况，会产生预期外的逻辑错误，此时应配合 [has_contested_owner](/wiki/trigger/has_contested_owner) 做补充判断。

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

pc_is_state_claimed is commonly used in mod scenarios related to peace conferences, such as post-war peace conference or territorial allocation systems, where it determines whether a state has been claimed by a party without dispute, thereby deciding whether to allow further diplomatic or construction actions. A typical scenario is using it within an available block to restrict a decision so it can only be triggered when the current state has been claimed without dispute.

# Using within a decision available block scoped to STATE
available = {
    pc_is_state_claimed = yes
    is_owned_by = ROOT
}

Synergy

[pc_is_state_claimed_by](/wiki/trigger/pc_is_state_claimed_by): Can be used in conjunction to further precisely determine which country made the claim after confirming the state is claimed, resulting in more rigorous logic.
[has_contested_owner](/wiki/trigger/has_contested_owner): pc_is_state_claimed checks for "uncontested" claims; pairing it with this trigger allows you to distinguish between contested and uncontested states, building more complete conditional branches.
[is_owned_by](/wiki/trigger/is_owned_by): Claims and actual control are two different things; typically you need to confirm both the state's ownership and claimed status to avoid logical gaps.
[add_claim_by](/wiki/effect/add_claim_by): When used together in an effect block, if claim conditions are not met, you can use this effect to add claims, forming a complete "check → remedy" workflow.

Common Pitfalls

Confusing "claims" with "cores": Beginners often conflate pc_is_state_claimed with [is_core_of](/wiki/trigger/is_core_of), but the former is specific to the Peace Conference system context. Using it outside peace conference flows may always return false, rather than the expected territorial ownership judgment.
Overlooking the "uncontested" requirement: This trigger requires that the claim be uncontested; if a state is claimed by multiple parties with disputes, the result is false. If you only use it to check "whether anyone claimed it" without considering disputes, you may encounter unexpected logic errors. In such cases, pair it with [has_contested_owner](/wiki/trigger/has_contested_owner) for supplementary checks.

trigger · pc_is_state_claimed