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

实战 · 配合 · 坑

实战内容由 AI 生成,并已对照 vanilla 命令词表校验 —— 请当作起点而非权威依据。上方的定义节才是游戏自带文档原文。

实战用法

start_resistance 常用于剧本事件或决议中,模拟被占领地区的民众开始武装反抗,例如某国在失去一个核心州后通过事件触发当地抵抗运动。当你需要为本应无法产生抵抗的地区(如占领国的本土核心州)强制启动抵抗时,此命令尤为关键。

# 在某国领土被占领后的事件中触发波兰核心州的抵抗运动
state_event = {
    id = resistance_events.1
    ...
    immediate = {
        force_enable_resistance = yes
        start_resistance = POL
    }
}

配合关系

  • [force_enable_resistance](/wiki/effect/force_enable_resistance):当目标州对某国而言本不满足产生抵抗的条件(如该国是该州的核心国),必须先调用此命令解锁抵抗机制,再使用 start_resistance 才能生效。
  • [add_resistance](/wiki/effect/add_resistance)start_resistance 仅负责"激活"抵抗活动,若需要在启动的同时赋予一定的初始抵抗值,需配合此命令一起使用。
  • [set_occupation_law](/wiki/effect/set_occupation_law):占领法规直接影响抵抗增长速度,在脚本中配合使用可精确模拟不同占领政策下抵抗运动的爆发情景。
  • [has_active_resistance](/wiki/trigger/has_active_resistance):常在触发条件块中作为检测前置,确认某州当前是否已有活跃抵抗,避免重复触发同一事件链。

常见坑

  1. 忘记配合 force_enable_resistance:对于占领国在该州拥有核心的情况,直接写 start_resistance = XXX 不会生效,必须在同一执行块中先写 force_enable_resistance = yes,这是新手最常漏掉的步骤。
  2. Scope 使用错误:此命令必须在 STATE scope 下调用,若直接写在国家 scope(如 country_eventimmediate 块中,而未切入具体州)将导致命令无效甚至报错,需用 every_state/具体州 ID 等方式先进入州 scope。

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.