Wiki

trigger · army_manpower_in_state

Definition

  • Supported scope:COUNTRY
  • Supported target:none

Description

Checks for amount manpower currently the target state with option to specify a type.
Example:
army_manpower_in_state = {
	state = <id> (variables supported)
	amount < <int> (variables supported)
	type > <equipment_type> (armor, infantry, etc.)

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

army_manpower_in_state is commonly used to determine whether a state has sufficient troop strength stationed in it. For example, it can validate garrison strength when creating a fortification consolidation decision, or verify in events/missions whether the player has deployed adequate manpower in critical states. The following example checks whether infantry manpower in a state falls below a threshold, triggering a reinforcement warning:

# In a trigger block of a decision/event
army_manpower_in_state = {
    state = 11
    amount < 5000
    type = infantry
}

Synergy

  • [divisions_in_state](/wiki/trigger/divisions_in_state): These two are frequently used together—first use divisions_in_state to confirm whether the state has any divisions deployed, then use this trigger to precisely assess manpower quantity, avoiding misinterpretation caused by relying solely on unit count (which could indicate empty divisions occupying the space).
  • [controls_state](/wiki/trigger/controls_state): Typically first confirm that your side actually controls the target state, then check the manpower within it, preventing incorrect judgments about manpower in enemy-occupied territories.
  • [add_manpower](/wiki/effect/add_manpower): When insufficient manpower is detected in a state, use this in conjunction in the effect block to replenish human resources, forming a complete "detection→resupply" logic chain.
  • [has_army_manpower](/wiki/trigger/has_army_manpower): has_army_manpower checks the national manpower pool, which complements this trigger's state-level garrison manpower. Using both together allows you to simultaneously control both macro reserves and local deployments.

Common Pitfalls

  1. Incorrect type field entry: The type field accepts equipment category keywords (such as infantry, armor), not specific equipment technology names or division template names. Entering a non-existent type causes the condition to silently fail (always evaluates to false), making it difficult to debug.
  2. Confusion over amount comparison operator direction: The syntax places the comparison operator after the amount keyword and before the value (e.g., amount < 5000). Beginners often mistakenly omit the operator by copying standard assignment syntax or reverse the direction, resulting in completely inverted condition logic.