Wiki

trigger · has_manpower_for_recruit_change_to

Definition

  • Supported scope:COUNTRY
  • Supported target:none

Description

check if manpower is enough to switch recruitment laws not to be negative

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

When designing decisions or national focuses related to conscription laws, this trigger is commonly used to ensure that before the player switches to a higher conscription requirement law, the current manpower reserves will not become negative due to deduction, avoiding the anomalous state of manpower "debt". For example, in a decision that allows manual switching of conscription laws:

available = {
    has_manpower_for_recruit_change_to = yes
}

Synergy

  • [current_conscription_amount](/wiki/trigger/current_conscription_amount): First check the current actual conscription rate, then combine with this trigger to form a dual-verification logic for "whether the target law can be safely switched".
  • [conscription_ratio](/wiki/trigger/conscription_ratio): Used to compare the current manpower consumption ratio; combining with this trigger can provide AI or players with more precise timing judgments for law switching.
  • [add_ideas](/wiki/effect/add_ideas): After the trigger verification passes, use this effect to actually apply the new conscription law idea; this is the most typical "verify then execute" synergy chain.
  • [has_manpower_for_recruit_change_to](/wiki/trigger/has_manpower_for_recruit_change_to) (nested within limit): Within looping scopes like every_allied_country, use the limit block to restrict conscription-related operations only to allies with sufficient manpower.

Common Pitfalls

  1. Mistakenly assuming you can pass target law parameters: This trigger accepts no field values; simply write = yes; beginners often try to write it in the form = { idea = xxx }, causing script errors or judgment failure.
  2. Using outside COUNTRY scope: This trigger is only valid within country scope; if mistakenly written within STATE or CHARACTER scope (for example, placed in a sub-block of any_owned_state), the game will silently ignore it or report an error, and the logic will not trigger as expected.