Wiki

trigger · casualties

Definition

  • Supported scope:COUNTRY
  • Supported target:none

Description

Check the amount of casualties a country has suffered in all of it's wars

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

casualties is commonly used in war-themed achievements and decision unlock conditions, such as determining whether a country has experienced sufficiently devastating war attrition, or triggering "war fatigue" narrative branches in events. It can also be used for AI strategy weight adjustments, allowing heavily damaged nations to automatically lean towards peace or diplomatic routes.

# Allow ceasefire decision only when casualties exceed threshold
available = {
    casualties > 500000
}

Synergy

  • [has_casualties_war_support](/wiki/trigger/has_casualties_war_support): Frequently appears alongside this trigger in the same trigger block. The former quantifies cumulative casualties, while the latter checks whether casualties have impacted war support, together depicting a "war fatigue" state.
  • [has_bombing_war_support](/wiki/trigger/has_bombing_war_support): Both bombing and casualties erode public morale. Using them together constructs multi-dimensional war weariness condition checks.
  • [add_war_support](/wiki/effect/add_war_support): After casualties reach the threshold, use effects to reduce war support, forming a complete logical chain: "high casualties → trigger → reduce war support".
  • [casualties_k](/wiki/trigger/casualties_k): Also a casualties-type trigger. casualties_k uses thousands as the unit, and when mixed with casualties, be aware of the different units. Choose the more appropriate one based on the magnitude of numbers.

Common Pitfalls

  1. Unit Confusion: The value of casualties is in headcount (e.g., 500000), while the whitelist simultaneously contains casualties_k (written in thousands as 500). Though functionally similar, the value formats are completely different. Mixing them causes conditions to never trigger or always evaluate true.
  2. Scope Placement Error: This trigger only works under COUNTRY scope. If mistakenly placed in STATE or CHARACTER scope (such as inside an any_owned_state sub-block), the script won't error but the judgment will be unpredictable. Ensure the outer scope points to a country tag.