Wiki

effect · add_state_core

Definition

  • Supported scope:COUNTRY
  • Supported target:none

Description

add core on state

实战 · 配合 · 坑

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

实战用法

add_state_core 常用于国家焦点、决策或事件中,让某国对特定省份建立核心,从而获得该省的减员惩罚豁免和战争借口。典型场景包括民族统一焦点(如让德国对奥地利建立核心)、战后领土重组,或通过决策逐步扩张历史主张。

# 在国家焦点完成时,让当前国家对 4 号州(维也纳地区)建立核心
focus = {
    id = GER_anschluss_cores
    ...
    completion_reward = {
        add_state_core = 4
        add_state_claim = 4  # 同时可先给主张作过渡
    }
}

配合关系

  • [add_state_claim](/wiki/effect/add_state_claim) — 通常先给予主张再给核心,形成"主张→核心"的渐进外交叙事,逻辑更自然。
  • [every_core_state](/wiki/effect/every_core_state) — 可遍历当前核心州批量操作,与 add_state_core 配合构建动态核心扩张链。
  • [create_wargoal](/wiki/effect/create_wargoal) — 建立核心后往往紧接着生成对该州的吞并战争借口,形成完整的扩张流程。
  • [any_core_state](/wiki/trigger/any_core_state) — 常作为前置触发检查,避免对已经是核心的州重复添加或产生冗余逻辑。

常见坑

  1. Scope 混淆add_state_core 的 scope 必须是 COUNTRY,新手容易误写在 every_owned_state 等州 scope 内部,导致脚本报错或静默失效——正确做法是在国家 scope 下直接填州 ID(整数),而不是 yes
  2. 核心不等于控制权:添加核心只改变"核心归属"标签,并不自动转移州的控制权或所有权,新手常误以为执行后该州会自动归属本国,实际上还需配合 transfer_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

add_state_core is commonly used in national focuses, decisions, or events to establish core ownership of a specific state for a country, granting that country casualty penalties exemption and casus belli on the state. Typical scenarios include national unification focuses (such as having Germany establish cores on Austria), post-war territorial reorganization, or gradual expansion of historical claims through decisions.

# When a national focus completes, establish a core for the current country on state 4 (Vienna region)
focus = {
    id = GER_anschluss_cores
    ...
    completion_reward = {
        add_state_core = 4
        add_state_claim = 4  # Can first add a claim as a transitional step
    }
}

Synergy

  • [add_state_claim](/wiki/effect/add_state_claim) — Typically grant a claim first before adding a core, forming a progressive "claim → core" diplomatic narrative that feels more natural.
  • [every_core_state](/wiki/effect/every_core_state) — Can iterate through current core states for batch operations, working with add_state_core to build dynamic core expansion chains.
  • [create_wargoal](/wiki/effect/create_wargoal) — After establishing a core, immediately generate a casus belli for annexing that state, forming a complete expansion workflow.
  • [any_core_state](/wiki/trigger/any_core_state) — Commonly used as a prerequisite trigger to avoid redundant additions or logic when a state is already a core.

Common Pitfalls

  1. Scope Confusion: The scope of add_state_core must be COUNTRY. Beginners often mistakenly place it inside state scopes like every_owned_state, causing script errors or silent failures. The correct approach is to directly specify the state ID (integer) within country scope, not yes.
  2. Cores Do Not Equal Control: Adding a core only changes the "core ownership" label and does not automatically transfer state control or ownership. Beginners often mistakenly assume the state will automatically belong to their country after execution. In reality, additional commands like transfer_state are needed to actually claim the territory.