Wiki

trigger · num_of_supply_nodes

Definition

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

Description

check amount of supply nodes

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

num_of_supply_nodes is commonly used to check whether a nation has established sufficient railway hubs/supply nodes, thereby unlocking specific decisions or national focus rewards. It is well-suited for "infrastructure completion check" type conditional thresholds. For example, in an industrial development task that requires the player to first expand the supply network before triggering the next phase:

available = {
    num_of_supply_nodes > 5
}

Synergy

  • [has_built](/wiki/trigger/has_built): Often paired with num_of_supply_nodes to simultaneously check specific building counts and node quantities, providing a comprehensive assessment of a nation's logistical infrastructure completeness.
  • [controls_state](/wiki/trigger/controls_state): Supply nodes are distributed across states; combined with checks on whether specific states are controlled, you can verify the logic "whether nodes have been established in a particular region."
  • [add_political_power](/wiki/effect/add_political_power): Serves as a reward effect upon condition fulfillment; when a nation reaches the target node count, grant political power rewards to incentivize players to invest in logistics development.
  • [building_count_trigger](/wiki/trigger/building_count_trigger): Both are triggers for checking infrastructure levels, commonly written within the same AND block, forming a dual threshold of "node count + building level."

Common Pitfalls

  1. Confusing scope levels: num_of_supply_nodes can only be used within COUNTRY scope. Beginners sometimes call it directly within STATE scope (e.g., inside any_owned_state), resulting in script errors or unexpected behavior—ensure you return to country scope before performing the check.
  2. Overlooking dynamic node changes: The number of supply nodes changes in real time as provinces are gained or lost during war. Placing this trigger in a location evaluated only once (such as allowed) may cause the conditional logic to not behave as expected. Prioritize placing it in available or trigger blocks for continuous evaluation.