Wiki

effect · start_resistance

Definition

  • Supported scope:STATE
  • Supported target:any

Description

starts resistance activity for a core country. 
Use along with force_enable_resistance if you are enabling resistance
in a state that is not possible (ie core).
Example : start_resistance = POL or start_resistance = yes

Hands-On Notes

Hands-on notes are AI-generated and checked against the vanilla command vocabulary — treat them as a starting point, not authoritative reference. The definition above is the game's own documentation.

Hands-On Usage

start_resistance is commonly used in scripted events or decisions to simulate armed resistance emerging in occupied territories—for example, a nation triggering a local resistance movement after losing a core state. This command becomes particularly crucial when you need to force-start resistance in regions that would normally be unable to generate it (such as the occupying power's own core states).

# Trigger resistance in Polish core states after the territory is occupied
state_event = {
    id = resistance_events.1
    ...
    immediate = {
        force_enable_resistance = yes
        start_resistance = POL
    }
}

Synergy

  • [force_enable_resistance](/wiki/effect/force_enable_resistance): When the target state does not normally meet the conditions for resistance to spawn for a given nation (e.g., that nation has the state as a core), you must first call this command to unlock the resistance mechanism before start_resistance will take effect.
  • [add_resistance](/wiki/effect/add_resistance): start_resistance only "activates" the resistance activity; if you need to assign an initial resistance value while starting it, you must use this command in conjunction.
  • [set_occupation_law](/wiki/effect/set_occupation_law): Occupation laws directly affect resistance growth rates. Using them together in scripts allows you to precisely simulate resistance outbreaks under different occupation policies.
  • [has_active_resistance](/wiki/trigger/has_active_resistance): Commonly used in conditional trigger blocks as a precondition check to confirm whether a state currently has active resistance, preventing duplicate event chain triggers.

Common Pitfalls

  1. Forgetting to pair with force_enable_resistance: When the occupying power has a core in the state, simply writing start_resistance = XXX will not work. You must first write force_enable_resistance = yes in the same execution block—this is the step most beginners overlook.
  2. Incorrect scope usage: This command must be called under a STATE scope. Writing it directly in a country scope (such as the immediate block of a country_event without switching to a specific state) will render the command ineffective or cause errors. Use every_state or specific state IDs to enter state scope first.