trigger · amount_manpower_in_deployment_queue

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

1. 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.
2. 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.