trigger · `received_expeditionary_forces`

Definition

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

Description

Checks that the country in scope has received the specified amount of expeditionary forces from the specified country
E.g. true if Germany is commaning more than 100 expeditionary forces from Poland:
GER = {
  received_expeditionary_forces = {
    sender = POL
    value > 100
  }
}

实战 · 配合 · 坑

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

实战用法

received_expeditionary_forces 常用于设计"外援依赖"相关的决策或焦点树，例如当某国从盟友处接收了足量远征军时才解锁特定战略选项，或在事件中根据外援规模动态给予加成。下面示例检测苏联是否从中国获得了超过 50 单位的远征军：

# 在某个决策的 available 块中
available = {
    SOV = {
        received_expeditionary_forces = {
            sender = CHI
            value > 50
        }
    }
}

配合关系

[has_attache_from](/wiki/trigger/has_attache_from)：两者常搭配区分"武官支援"与"远征军实体兵力"两种不同的军事合作形式，互为补充的判断条件。
[foreign_manpower](/wiki/trigger/foreign_manpower)：检查外国人力存量，与远征军数量一起评估宿主国整体外来军事资源是否达到触发门槛。
[add_manpower](/wiki/effect/add_manpower)：当远征军接收条件满足时，通常随之给予本国额外人力奖励，作为"外援到位"的游戏反馈。
[any_allied_country](/wiki/trigger/any_allied_country)：遍历所有盟国，嵌套 received_expeditionary_forces 来检测是否存在任意盟友提供了足量援军，适合多方联盟场景。

常见坑

sender 必须是实际派遣国 TAG，不能写 scope 关键字：新手容易把 sender = THIS 或 sender = FROM 写进去，但该字段只接受硬编码的国家 TAG（如 GER、POL），用 scope 关键字会导致条件永远不触发。
比较运算符写法不能加等号前缀的空格：value > 100 是正确写法，若误写成 value >= 100 而游戏版本不支持该运算符，或将 > 与数字之间漏掉空格（value >100），都会造成解析错误，日志中不一定给出明显报错，需注意严格对照官方格式。

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

received_expeditionary_forces is commonly used in designing decisions or focus trees related to "dependency on foreign aid"—for example, unlocking specific strategic options when a nation receives sufficient expeditionary forces from an ally, or dynamically granting bonuses in events based on the scale of aid received. The example below checks whether the Soviet Union has received more than 50 units of expeditionary forces from China:

# Within the available block of a decision
available = {
    SOV = {
        received_expeditionary_forces = {
            sender = CHI
            value > 50
        }
    }
}

Synergy

[has_attache_from](/wiki/trigger/has_attache_from): Often paired together to distinguish between "military attaché support" and "expeditionary force combat units"—two different forms of military cooperation that complement each other as judgment conditions.
[foreign_manpower](/wiki/trigger/foreign_manpower): Checks the reserve of foreign manpower; used alongside expeditionary force count to assess whether the host nation's total foreign military resources meet the trigger threshold.
[add_manpower](/wiki/effect/add_manpower): When expeditionary force reception conditions are met, it is typically followed by granting additional manpower to the nation as game feedback for "aid delivered."
[any_allied_country](/wiki/trigger/any_allied_country): Iterates through all allied nations, nesting received_expeditionary_forces to detect whether any ally has provided sufficient aid units—suitable for multi-party alliance scenarios.

Common Pitfalls

sender must be the actual dispatching nation TAG and cannot use scope keywords: Beginners often write sender = THIS or sender = FROM, but this field only accepts hard-coded country TAGs (such as GER, POL). Using scope keywords will cause the condition to never trigger.
Comparison operator syntax cannot have spaces before the operator: value > 100 is the correct format. If mistakenly written as value >= 100 when the game version doesn't support that operator, or if a space is omitted between > and the number (value >100), it will cause a parsing error. The log may not show an obvious error message, so strict adherence to the official format is necessary.

trigger · received_expeditionary_forces