Wiki

trigger · pc_is_puppeted_by

Definition

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

Description

Checks if country is a puppet of a certain country, or has been released as a puppet by a certain country in the peace conference.
Example:
CZE = { pc_is_puppeted_by = GER }

实战 · 配合 · 坑

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

实战用法

在和平会议 mod 或傀儡体系相关的 focus/decision 中,常用此 trigger 来检查某国是否已成为特定宗主国的傀儡,从而决定是否触发后续剧情或限制某些选项。例如在捷克斯洛伐克相关的 mod 事件中,判断 CZE 是否被 GER 傀儡化来决定是否提供援助选项:

available = {
    CZE = {
        pc_is_puppeted_by = GER
    }
}

配合关系

  • [has_autonomy_state](/wiki/trigger/has_autonomy_state):配合使用可同时检查傀儡国的自治度等级,细化对傀儡关系类型(如受保护国、帝国属地等)的判断。
  • [any_subject_country](/wiki/trigger/any_subject_country):在宗主国 scope 下遍历所有附属国,再用 pc_is_puppeted_by 反向验证,可构建双向一致性检查逻辑。
  • [end_puppet](/wiki/effect/end_puppet):当条件满足(确认傀儡关系存在)后,配合此 effect 解除傀儡关系,是"解放"类 decision 的标准组合。
  • [exists](/wiki/trigger/exists):在调用 pc_is_puppeted_by 前先确认目标国家存在,防止因国家不存在导致脚本报错或逻辑异常。

常见坑

  1. scope 方向写反:此 trigger 必须在被傀儡国的 scope 内使用(即 CZE = { pc_is_puppeted_by = GER }),新手常误写为在宗主国 scope 下调用,导致判断结果始终为假。
  2. 混淆和平会议语境与常规游戏状态:trigger 描述中包含"在和平会议中被释放为傀儡"的情形,这意味着即使当前傀儡关系尚未正式生效,和平会议阶段也可能返回真值,在和平会议外的普通 focus/event 中需注意此行为是否符合预期。

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 peace conference mods or puppet system-related focus/decision trees to check whether a nation has become a puppet of a specific overlord, thereby determining whether to trigger subsequent events or restrict certain options. For example, in Czech-related mod events, checking whether CZE is puppeted by GER to decide whether to offer aid options:

available = {
    CZE = {
        pc_is_puppeted_by = GER
    }
}

Synergy

  • [has_autonomy_state](/wiki/trigger/has_autonomy_state): Use in conjunction to simultaneously check the puppet state's autonomy level, refining judgment of puppet relationship types (such as protected states, imperial territories, etc.).
  • [any_subject_country](/wiki/trigger/any_subject_country): Iterate through all subject countries under the overlord scope, then use pc_is_puppeted_by for reverse verification to build bidirectional consistency check logic.
  • [end_puppet](/wiki/effect/end_puppet): After conditions are met (confirming the puppet relationship exists), combine with this effect to revoke the puppet relationship, forming the standard combination for "liberation" decisions.
  • [exists](/wiki/trigger/exists): Confirm the target nation exists before calling pc_is_puppeted_by to prevent script errors or logic anomalies caused by a non-existent nation.

Common Pitfalls

  1. Reversed scope direction: This trigger must be used within the scope of the puppeted nation (i.e., CZE = { pc_is_puppeted_by = GER }). Beginners often mistakenly call it under the overlord scope, causing the evaluation to always return false.
  2. Confusing peace conference context with regular game state: The trigger description includes scenarios where a nation is "released as a puppet during peace conference," meaning that even if the puppet relationship has not formally taken effect, the peace conference phase may return true. In ordinary focus/event trees outside peace conferences, pay attention to whether this behavior aligns with expectations.