Hands-On Usage
has_casualties_war_support is commonly used to dynamically assess the severity of war support decline in a country caused by excessive casualties. For example, it can set a "morale crisis" threshold in a focus or decision, triggering special events or national focuses when casualty penalties exceed a certain ratio. It also pairs well with AI strategies, making the AI more inclined to negotiate or seek a ceasefire when casualty penalties become too severe.
# Trigger a morale crisis decision when casualty penalties exceed 30% of war support
available = {
has_casualties_war_support > 0.3
}
Synergy
[has_bombing_war_support](/wiki/trigger/has_bombing_war_support): Bombing-induced war support penalties and casualty penalties are parallel sources of pressure. They are often checked together to determine the compounded causes of overall war support crises.
[has_convoys_war_support](/wiki/trigger/has_convoys_war_support): Convoy losses similarly erode war support. The combination of all three can form a "total war fatigue" condition, ideal for designing peace-oriented event chains.
[add_war_support](/wiki/effect/add_war_support): When casualty penalties trigger a threshold, this effect is commonly used as a compensatory measure (e.g., propaganda campaigns) to offset the continuous decline in war support.
[add_stability](/wiki/effect/add_stability): When casualty penalties are severe, players often face stability crises simultaneously. Combining this effect allows handling both pressure lines within events.
Common Pitfalls
- Direction Confusion: This value reflects the "penalty amount" rather than "remaining war support." A higher value indicates greater negative impact from casualties on war support. Beginners often misinterpret
> 0.5 as "war support above 50%" when it actually means "war support penalty from casualties exceeds 50%"—the semantics are completely opposite.
- Scope Omission: This trigger only functions within
COUNTRY scope. If written in a state scope or unit leader scope condition block, it will silently fail without error messages, and the condition will never evaluate to true. This is easily overlooked during debugging.