trigger · `amount_manpower_in_deployment_queue`

Definition

Supported scope:COUNTRY
Supported target:none

Description

Checks for amount manpower currently in deploymentview. amount_manpower_in_training > 10

实战 · 配合 · 坑

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

实战用法

常用于检测某个国家的部署队列中是否积压了过多兵员，从而触发相关警告事件或解锁补充兵力的决议。例如在兵役制度 mod 中，当部署队列人力超过阈值时自动给予政治力惩罚或触发提示事件：

# 在某个决议的 available 块中，要求部署队列人力未超载才可激活
available = {
    amount_manpower_in_deployment_queue < 50000
}

# 在 event trigger 中检测人力积压
trigger = {
    amount_manpower_in_deployment_queue > 100000
}

配合关系

[has_army_manpower](/wiki/trigger/has_army_manpower)：两者结合可同时判断国家总人力储备与当前队列积压量，形成"有没有兵、训不训得过来"的双重条件。
[conscription_ratio](/wiki/trigger/conscription_ratio)：部署队列积压往往与征兵率直接相关，联用可判断是否因过高征兵率导致队列堵塞。
[add_manpower](/wiki/effect/add_manpower)：当条件触发（队列过满或过空）时，通过此 effect 直接增减人力来做动态平衡。
[add_political_power](/wiki/effect/add_political_power)：在队列人力超载时扣除政治力，模拟后勤压力带来的行政负担，是常见的惩罚机制搭配。

常见坑

把它当瞬时快照理解时忽略动态变化：部署队列人力会随每日 tick 不断变化，在事件或决议中用它做判断时，前一刻满足条件不代表事件执行时仍满足，建议在 mean_time_to_happen 较短的事件中使用，或搭配 limit 再次校验。
与 has_army_manpower 混淆：has_army_manpower 检测的是国家人力池中可用的总人力，而本 trigger 检测的是已进入部署队列但尚未完成训练的人力，两者含义不同，不能互相替代。

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

Commonly used to detect whether a nation's deployment queue has accumulated excessive manpower, triggering related warning events or unlocking resolutions for troop reinforcement. For example, in a conscription system mod, when deployment queue manpower exceeds a threshold, automatically apply political power penalties or trigger notification events:

# In an available block of a decision, require deployment queue manpower not to exceed capacity before activation
available = {
    amount_manpower_in_deployment_queue < 50000
}

# In event trigger to detect manpower backlog
trigger = {
    amount_manpower_in_deployment_queue > 100000
}

Synergy

[has_army_manpower](/wiki/trigger/has_army_manpower): Combined with this trigger, you can simultaneously check both the nation's total manpower reserves and current queue backlog, creating a dual condition of "do we have troops, and can we train them fast enough."
[conscription_ratio](/wiki/trigger/conscription_ratio): Deployment queue backlogs are often directly correlated with conscription rates. Using them together helps determine whether excessive conscription rates are causing queue congestion.
[add_manpower](/wiki/effect/add_manpower): When conditions trigger (queue too full or too empty), use this effect to directly add or remove manpower for dynamic balancing.
[add_political_power](/wiki/effect/add_political_power): Deduct political power when queue manpower is overloaded, simulating administrative burden from logistical pressure—a common pairing for penalty mechanics.

Common Pitfalls

Treating it as an instantaneous snapshot and ignoring dynamic changes: Deployment queue manpower continuously fluctuates with each daily tick. When using it for judgment in events or decisions, satisfying the condition one moment doesn't guarantee it still holds when the event executes. It's recommended to use this in events with short mean_time_to_happen, or pair it with limit for additional verification.
Confusing it with has_army_manpower: has_army_manpower checks the total available manpower in the nation's manpower pool, while this trigger checks manpower already in the deployment queue but not yet finished training. These have different meanings and cannot be used interchangeably.

trigger · amount_manpower_in_deployment_queue