Wiki

trigger · resistance_target

Definition

  • Supported scope:STATE
  • Supported target:any

Description

Compares the target resistance level of a state to a value. Example: resistance_target > 50

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

resistance_target is commonly used in occupation management mods to dynamically trigger events or restrict decision availability based on a state's target resistance value. For example, it can prohibit certain suppression measure options when enemy-occupied regions have excessively high resistance targets. It can also be used in AI condition checks, allowing occupation policy switches only when the target resistance value exceeds a certain threshold.

# Only restrict a certain decision when this state's target resistance exceeds 50
available = {
    resistance_target < 50
}

Synergy

  • [resistance](/wiki/trigger/resistance): resistance_target reflects the target value, while resistance reflects the current actual resistance intensity. Used together, they enable precise resistance trend assessment (high target but low current value indicates resistance is rising).
  • [has_active_resistance](/wiki/trigger/has_active_resistance): First confirm whether active resistance exists in the state, then use resistance_target to judge its intensity, avoiding ineffective checks in states without resistance.
  • [add_resistance_target](/wiki/effect/add_resistance_target): The corresponding effect; commonly used to first check resistance_target as a condition in the same script block, then decide whether to adjust the target value.
  • [occupation_law](/wiki/trigger/occupation_law): Occupation laws are directly related to target resistance. Combined usage enables logic like "trigger specific consequences when occupation law is harsh and target resistance is too high."

Common Pitfalls

  1. Confusing resistance_target with resistance: Beginners often use these interchangeably, but in reality the former is the system-calculated target "equilibrium value" of resistance, while the latter is the current real-time resistance intensity. They can differ significantly, and using the wrong one causes condition timing to be completely inaccurate.
  2. Forgetting that scope must be STATE: This trigger only works under state scope. Writing it directly in country scope or province scope condition blocks will silently fail or throw an error. You must first switch to the correct scope using methods like any_neighbor_state.