trigger · `pc_is_puppeted`

Definition

Supported scope:COUNTRY
Supported target:none

Description

Checks if country is a puppet, or has been released as a puppet in the peace conference.
Example:
CZE = { pc_is_puppeted = yes }

实战 · 配合 · 坑

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

实战用法

在和平会议 mod 或傀儡独立事件中，常用此 trigger 判断某国是否处于傀儡状态，从而决定是否触发解放事件或给予特定 idea。例如在傀儡国反抗独立的 focus 中限制该选项仅对傀儡国可用：

available = {
    CZE = {
        pc_is_puppeted = yes
    }
}

配合关系

[has_autonomy_state](/wiki/trigger/has_autonomy_state)：与 pc_is_puppeted 配合可进一步细化傀儡类型（如区分整合傀儡与受保护国），避免逻辑过于宽泛。
[exists](/wiki/trigger/exists)：在检查傀儡状态前先确认目标国家存在，防止因国家不存在导致脚本报错。
[end_puppet](/wiki/effect/end_puppet)：当傀儡条件满足后，常作为 effect 结果解除傀儡关系，与此 trigger 形成"判断→执行"的完整逻辑链。
[has_capitulated](/wiki/trigger/has_capitulated)：和平会议场景下常与之并用，区分"已投降但尚未处理"与"已被设定为傀儡"两种状态。

常见坑

scope 使用错误：此 trigger 必须在 COUNTRY scope 下调用，新手容易在 STATE scope（如 any_owned_state 内部）直接写 pc_is_puppeted = yes，导致游戏报 scope 错误或静默失败，需用 OWNER 等关键字跳回国家 scope 再判断。
仅限和平会议期间的语义误解：官方描述中"released as a puppet in the peace conference"意味着该 trigger 在和平会议结算阶段也会对刚被指定为傀儡但尚未正式生效的国家返回真，若在常规游戏逻辑中依赖此 trigger 判断"已完全生效的傀儡"，可能得到非预期结果，需结合 has_autonomy_state 做双重验证。

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

In peace conference mods or puppet independence events, this trigger is commonly used to determine whether a country is in puppet status, thereby deciding whether to trigger liberation events or grant specific ideas. For example, in a puppet state's focus for resisting independence, restrict this option to be available only for puppet nations:

available = {
    CZE = {
        pc_is_puppeted = yes
    }
}

Synergy

[has_autonomy_state](/wiki/trigger/has_autonomy_state): Combined with pc_is_puppeted, this can further refine puppet types (e.g., distinguishing integrated puppets from protectorates) and avoid overly broad logic.
[exists](/wiki/trigger/exists): Confirm the target country exists before checking puppet status to prevent script errors due to non-existent nations.
[end_puppet](/wiki/effect/end_puppet): After puppet conditions are met, this commonly serves as the effect result to remove puppet relations, forming a complete "check → execute" logic chain with this trigger.
[has_capitulated](/wiki/trigger/has_capitulated): Frequently used together in peace conference scenarios to distinguish between "already surrendered but not yet processed" and "already set as puppet" states.

Common Pitfalls

Scope usage errors: This trigger must be called under COUNTRY scope. Beginners often mistakenly write pc_is_puppeted = yes directly within STATE scope (such as inside any_owned_state), resulting in scope errors or silent failures. Use keywords like OWNER to return to country scope before checking.
Misunderstanding the peace conference-only semantics: The official description "released as a puppet in the peace conference" means this trigger will also return true during peace conference resolution for countries just designated as puppets but not yet formally implemented. If relying on this trigger in regular game logic to determine "fully effective puppets," unexpected results may occur. Double verification using has_autonomy_state is recommended.

trigger · pc_is_puppeted