trigger · is_on_continent

Hands-On Usage

is_on_continent is commonly used to restrict certain decisions, events, or building construction conditions to states on specific continents—for example, "colonial development decisions available only to African states" or "special modifiers granted only to European states." When iterating through global states, it also filters out states from irrelevant continents, preventing unintended condition triggers.

# Example: A decision available only on Asian states
available = {
    is_on_continent = asia
}

Synergy

• [is_owned_by](/wiki/trigger/is_owned_by): Use together to precisely filter states that are "owned by a specific country AND located on a specific continent," commonly seen in colonization or sphere of influence mods.
• [any_neighbor_state](/wiki/trigger/any_neighbor_state): When iterating neighboring states, combining with is_on_continent can exclude cross-continental neighbors (such as edge cases like Gibraltar).
• [region](/wiki/trigger/region): Using both simultaneously enables dual-layer geographic filtering at continent and sub-region levels for more granular condition checks.
• [add_state_modifier](/wiki/effect/add_state_modifier): In effect blocks, confirm the continent first, then apply corresponding regional modifiers to implement differentiated continent-specific bonuses.

Common Pitfalls

1. Incorrect capitalization or spelling of continent names: Valid values are lowercase English (europe, asia, africa, north_america, south_america, australia). Writing Europe or Europa will silently fail—the condition will never return true, and the game typically won't report an error.
2. Direct use in COUNTRY scope: This trigger only works in STATE scope. If you write is_on_continent = europe directly in a country-level event's trigger block without first switching to state scope (e.g., via any_owned_state), the scope will mismatch and results will be unpredictable.