trigger · current_conscription_amount

Hands-On Usage

current_conscription_amount is commonly used to detect the current actual conscription population of a nation, making it ideal for use in focuses, decisions, or events to determine whether a nation's manpower source has reached a certain threshold, thereby unlocking or restricting subsequent options. For example, when a nation faces a threat of war, you can decide whether to trigger an emergency mobilization event based on the current conscription amount.

# available block in a decision: only allows execution when current conscription exceeds a specific value
available = {
    current_conscription_amount > 500000
}

Synergy

• [conscription_ratio](/wiki/trigger/conscription_ratio): Often used in tandem with this trigger; the former checks absolute numbers while the latter checks conscription as a percentage of population. Combined usage provides a more precise description of a nation's manpower state.
• [has_army_manpower](/wiki/trigger/has_army_manpower): Used to compare actual deployed manpower against the conscription pool size, determining whether a nation has a gap of "manpower available but not mobilized".
• [add_manpower](/wiki/effect/add_manpower): Once conscription conditions are met, this effect directly replenishes the nation's manpower pool, forming a logical closed loop of "check then reward".
• [amount_manpower_in_deployment_queue](/wiki/trigger/amount_manpower_in_deployment_queue): Combined with this trigger, you can distinguish between "total conscription amount" and "manpower currently in the deployment queue", avoiding judgment errors caused by double-counting.

Common Pitfalls

1. Confusing conscription amount with total manpower pool: current_conscription_amount reflects the actual manpower currently conscripted, not the cap or remaining reserve of a nation's manpower pool. Beginners often conflate its meaning with other triggers like has_army_manpower, leading to reversed condition logic.
2. Forgetting scope restrictions: This trigger only functions within COUNTRY scope; if written in a limit block under STATE or CHARACTER scope it will silently fail or error, making it difficult to detect during debugging.