trigger · state_and_terrain_strategic_value

Hands-On Usage

state_and_terrain_strategic_value is commonly used in strategic resource allocation, decision unlocking, or AI balancing logic to determine whether a state possesses sufficient strategic significance, thereby deciding whether to trigger specific events or allow certain decisions. For example, in custom occupation system mods, it can be used to filter out high-value states and apply additional administrative pressure or rewards to them.

# Decision available block: only unlocked for states with sufficiently high strategic value
available = {
    state_and_terrain_strategic_value > 5
}

Synergy

• [has_state_category](/wiki/trigger/has_state_category): Strategic value is often strongly correlated with state category (urban, rural, etc.). Using both together enables more precise target filtering and avoids false positives on low-value broad categories.
• [is_controlled_by](/wiki/trigger/is_controlled_by): Confirm state ownership before evaluating strategic value; commonly used in decision or event condition blocks to ensure effects only apply to high-value states controlled by your side or enemies.
• [set_state_category](/wiki/effect/set_state_category): When strategic value reaches a threshold, you can use effects to upgrade state category, enabling "strategic stronghold upgrade" gameplay mechanics in mods.
• [state_strategic_value](/wiki/trigger/state_strategic_value): Both involve state strategic assessment; state_strategic_value focuses on pure numerical comparison, while this trigger additionally factors in terrain, and using both together enables multi-dimensional filtering logic.

Common Pitfalls

1. Incorrect Scope Usage: This trigger can only be used within STATE scope. Beginners often write it directly in limit blocks under COUNTRY scope, causing script errors or silent failures—you must first switch to STATE scope via any_owned_state/all_claimant or similar methods before invoking it.
2. Mistaking It for a Boolean: This trigger actually supports numerical comparison (e.g., > N). Writing state_and_terrain_strategic_value = yes directly usually fails to express the intended logic; you should explicitly specify comparison operators and thresholds.