trigger · divisions_in_border_state

Hands-On Usage

divisions_in_border_state is commonly used to check whether a country has concentrated sufficient military forces in a border state, thereby triggering diplomatic events, decisions, or AI strategy adjustments. For example, in border tension mods, it can be used to detect whether the defending side has deployed enough divisions to unlock diplomatic protest options, or in decision chains to require players to deploy a certain number of troops on the border before progressing.

# In a focus's available condition, require sufficient divisions in a border state
available = {
    divisions_in_border_state = {
        state = 42        # Target border state ID
        size > 3          # At least 4 divisions
    }
}

Synergy

• [divisions_in_state](/wiki/trigger/divisions_in_state): Similar functionality; divisions_in_state checks the division count in any state and is often contrasted with divisions_in_border_state to differentiate between "inland concentration" and "border front deployment" in strategic assessment scenarios.
• [controls_state](/wiki/trigger/controls_state): Before confirming border division counts, use this trigger first to verify that your country actually controls the target state, avoiding meaningless quantity checks on states you cannot control.
• [has_border_war_with](/wiki/trigger/has_border_war_with): In border war scenarios, typically check for the existence of a border war using this trigger first, then combine with divisions_in_border_state to assess whether the front line has sufficient forces, forming a complete condition chain for border conflicts.
• [add_political_power](/wiki/effect/add_political_power): Serves as a reward effect after the above trigger conditions are met; for example, grant political power when the player successfully deploys sufficient divisions on the border, forming a complete decision logic of "deploy → detect → reward".

Common Pitfalls

1. The state parameter is the "ID of the state being checked" not the neighboring country's ID: Beginners often mistakenly believe the parameter refers to "the country across the border", but you actually need to specify the exact state ID, and that state must share a border with your current country, otherwise the trigger will never return the expected result.
2. The scope must be COUNTRY not STATE: This trigger counts the divisions of the "current country" in the specified state; if mistakenly placed in a STATE scope condition block (such as limit nested within every_owned_state), it will fail to evaluate or error due to scope mismatch.