Hands-On Usage
add_resistance_target is commonly used in occupation events or decisions to temporarily increase the resistance target value for a specific state, simulating the population's reaction to oppressive occupation policies or creating unrest scenarios in conjunction with narrative events. For example, after a "brutal crackdown" decision is triggered, you can set a time-limited additional resistance target for the occupied state and bind it with an ID for later manual removal via other events:
# In the effect block of an occupation decision
123_occupied_state = {
add_resistance_target = {
id = brutal_crackdown_target
amount = 15
occupied = POL
occupier = GER
days = 90
tooltip = "BRUTAL_CRACKDOWN_RESISTANCE_TT"
}
}
Synergy
[remove_resistance_target](/wiki/effect/remove_resistance_target): Used in tandem with this command. Once the id field is set, you can precisely remove previously added resistance targets when conditions are met (such as event triggers or decision completion), avoiding permanent stacking of effects.
[resistance_target](/wiki/trigger/resistance_target): Used to detect whether the current state's resistance target value has reached a certain threshold. It can serve as a subsequent trigger after add_resistance_target execution to determine whether to further trigger suppression events.
[add_compliance](/wiki/effect/add_compliance): Resistance targets and compliance are two sides of the occupation system. When adding resistance targets, you typically need to pair it with lowering compliance to jointly simulate the deterioration of occupation status.
[set_occupation_law](/wiki/effect/set_occupation_law): Modifying occupation laws is a common prerequisite operation that causes resistance target fluctuations. Combined with this command, it can fully recreate a narrative logic of "policy tightening → civil unrest".
Common Pitfalls
- Forgetting to set
id makes removal impossible: If the id field is not filled, you will be unable to precisely remove that entry later via remove_resistance_target. Multiple triggers will cause the effects to accumulate permanently, resulting in an abnormally high state resistance target that cannot be rolled back.
- Calling outside STATE scope: This command must be executed within a state scope. Calling it directly in a country or army scope will cause script errors or silent failures. Make sure to enter the correct scope first through state references (such as
123 = { ... }).