Wiki

trigger · has_manpower

Definition

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

Description

check amount of manpower

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

has_manpower is commonly used to determine whether a country has sufficient manpower to unlock decisions, trigger national focus effects, or constrain AI behavior, preventing the player or AI from taking unreasonable actions when manpower is depleted. For example, in a recruitment-related decision, you can use it as a prerequisite condition for available:

available = {
    has_manpower > 50000
}

Synergy

  • [amount_manpower_in_deployment_queue](/wiki/trigger/amount_manpower_in_deployment_queue): When paired together, it checks both stockpiled manpower and manpower consumed in the deployment queue, providing a more comprehensive assessment of actual available manpower surplus.
  • [add_manpower](/wiki/effect/add_manpower): When has_manpower determines that manpower is insufficient, it is commonly used in the corresponding effect block to replenish manpower, forming a "check → compensate" logic flow.
  • [conscription_ratio](/wiki/trigger/conscription_ratio): Combined checks of manpower values and conscription rates can determine whether a country is critically short on supplies even under high-intensity mobilization, useful for war pressure-related scripts.
  • [has_army_manpower](/wiki/trigger/has_army_manpower): Both belong to manpower-related checks; has_army_manpower refers to troops already in field armies, and when paired with has_manpower, it can distinguish between "reserve manpower" and "active forces" scenarios.

Common Pitfalls

  1. Unit Confusion: The numerical unit entered in the script is measured in individual "persons" rather than "thousands," and beginners often mistakenly write 50 based on the "50K" displayed in the interface, when it should actually be 50000. Otherwise, the condition will almost always evaluate to true and be difficult to detect.
  2. Scope Error: has_manpower is only valid under COUNTRY scope. If used directly within STATE or CHARACTER scope, it will silently fail or cause an error. You must ensure the outer scope is a country, or explicitly switch to country scope through targets like OWNER.