effect · `release_puppet_on_controlled`

Definition

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

Description

releases specified country as puppet using states you own or control

实战 · 配合 · 坑

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

实战用法

release_puppet_on_controlled 常用于二战后和平条约或傀儡帝国崩解的 mod 场景——例如某国在内战/战争结束后，需要用自己控制或占领的土地释放一个新傀儡国，而不必先完成正式吞并。它的优势在于可以把占领中但尚未正式割让的州也纳入傀儡国领土，省去先 annex_country 再释放的繁琐步骤。

# 德国在占领法国后，将维希法国作为傀儡释放（含控制州）
GER = {
    release_puppet_on_controlled = FRA
}

配合关系

[controls_state](/wiki/trigger/controls_state)：在执行释放前检查是否确实控制了目标州，避免因控制范围不足导致新傀儡领土为空的尴尬情况。
[diplomatic_relation](/wiki/effect/diplomatic_relation)：释放后可立即调整双边外交关系（如设置不可侵犯条约），为傀儡关系提供额外外交约束。
[has_autonomy_state](/wiki/trigger/has_autonomy_state)：用于事后校验被释放国是否已处于预期的自治等级，确保傀儡链条符合设计意图。
[add_state_core](/wiki/effect/add_state_core)：释放傀儡后可给新国家添加核心州，保证傀儡在地图上的领土主张逻辑自洽。

常见坑

混淆"拥有"与"控制"：该 effect 同时使用 owner 和 controller 的州，但如果作用 scope 的国家既不拥有也不控制目标州，对应州会被跳过而非报错——新手常以为"只要曾经占领过"就够，实际上释放时刻必须处于控制状态，否则新傀儡会缺少预期领土。
在错误的 scope 下调用：该 effect 只能在 COUNTRY scope 内执行；若写在 state 或 unit_leader 块中会静默失败，调试时不会有明显报错，极易造成剧本逻辑漏洞。

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

release_puppet_on_controlled is commonly used in post-WWII peace treaty scenarios or puppet empire collapse mods—for instance, when a nation needs to release a new puppet using territory it controls or occupies after a civil war or war's end, without having to complete formal annexation first. Its advantage lies in the ability to include states under occupation but not yet formally ceded within the puppet's territory, eliminating the tedious step of annex_country followed by release.

# Germany releases Vichy France as a puppet after occupying France (including controlled states)
GER = {
    release_puppet_on_controlled = FRA
}

Synergy

[controls_state](/wiki/trigger/controls_state): Check before execution whether the target states are actually controlled, avoiding the awkward situation where the new puppet's territory ends up empty due to insufficient control range.
[diplomatic_relation](/wiki/effect/diplomatic_relation): Immediately adjust bilateral diplomatic relations after release (such as establishing non-aggression pacts), providing additional diplomatic constraints for the puppet relationship.
[has_autonomy_state](/wiki/trigger/has_autonomy_state): Verify after the fact whether the released nation has reached the expected autonomy level, ensuring the puppet chain aligns with design intent.
[add_state_core](/wiki/effect/add_state_core): Add core states to the new nation after releasing the puppet, guaranteeing the puppet's territorial claims on the map remain logically consistent.

Common Pitfalls

Confusing "ownership" with "control": This effect uses states from both owner and controller, but if the scope nation neither owns nor controls target states, those states are simply skipped rather than triggering an error—newcomers often assume "occupation at any point in the past" suffices, when in reality the nation must be in active control at the moment of release, otherwise the new puppet will be missing expected territory.
Calling under the wrong scope: This effect only executes within COUNTRY scope; placing it in state or unit_leader blocks will fail silently without obvious error messages during debugging, easily creating logic gaps in your script.

effect · release_puppet_on_controlled