trigger · state_strategic_value

Hands-On Usage

state_strategic_value is commonly used in dynamic decision logic and event triggers, such as restricting occupation policies, building construction, or special decisions to apply only to states meeting strategic value thresholds. In occupation system mods or war goal mods, it can be used to filter high-value states as priority targets for conquest.

# Example: Allow activation of a targeted decision only when state strategic value is sufficiently high
available = {
    state_strategic_value > 0.5
}

Synergy

• [has_state_category](/wiki/trigger/has_state_category): State category (such as city, agricultural region, etc.) directly affects strategic value calculation; the two are often used together for dual filtering of target states.
• [state_and_terrain_strategic_value](/wiki/trigger/state_and_terrain_strategic_value): Also a strategic value-related trigger; can be used in parallel to distinguish between "pure state value" and "comprehensive value with terrain bonuses," forming more precise condition combinations.
• [is_controlled_by](/wiki/trigger/is_controlled_by): In practical scenarios, control ownership typically also needs to be confirmed; combined use allows precise identification of scenarios like "enemy-controlled high-value states."
• [set_state_category](/wiki/effect/set_state_category): Modifying state category on the effect side may influence subsequent strategic value judgment; commonly seen in test scenarios or mod logic that dynamically changes state positioning.

Common Pitfalls

1. Incorrect scope usage: This trigger can only be called under STATE scope. If used directly in condition blocks within COUNTRY or CHARACTER scope without first switching scope (such as through any_state iteration), it will cause script errors or silent failures. Newcomers often mistakenly believe the condition "never triggers" as a result.
2. Threshold understanding discrepancy: Strategic value is a floating-point number rather than an integer; direct comparison with integers (such as writing = 1) may fail to match intended states due to precision issues. It is recommended to use > or < for range judgment rather than strict equality.