trigger · area

Hands-On Usage

area is commonly used to check whether a state belongs to a specific strategic area, enabling you to trigger events, decisions, or national focus effects based on geographic regions. It's particularly useful for scenarios like "unlocking construction options after occupying a specific strategic area" or "limiting a national focus to affect only states within a certain strategic area."

# available block in a decision: only available when the target state is in strategic area 118 (Eastern Mediterranean)
available = {
    FROM = {
        area = 118
    }
}

Synergy

• [region](/wiki/trigger/region): region checks the region a state belongs to, while area checks the strategic area. These are often stacked together to precisely define geographic scope, creating a "macro region + micro region" dual filter.
• [is_owned_by](/wiki/trigger/is_owned_by): checks whether states within a strategic area are controlled by a specific country. Commonly combined with area in any_neighbor_state or event conditions.
• [has_state_category](/wiki/trigger/has_state_category): after locking a strategic area, further filters states by size category to avoid triggering high-cost effects on minor states.
• [set_state_category](/wiki/effect/set_state_category): in effect blocks, batch-modify state categories for states meeting area conditions. This is a typical pattern in regional development mods.

Common Pitfalls

1. Confusing area with region: area corresponds to "strategic area" in the game's map editor, and its ID system is completely separate from "region" IDs. Beginners often swap these IDs, causing conditions to never evaluate as true.
2. Using directly under COUNTRY scope: area only works under STATE scope. If you forget to switch to state scope first (e.g., via capital_scope, every_owned_state), writing area = ... directly under country scope will be silently ignored by the engine or cause errors, breaking your logic entirely.