Hands-On Usage
casualties_inflicted_by is commonly used in campaign achievement or scenario-trigger mods, such as determining whether a nation inflicted sufficient casualties on a rival during a historical campaign to unlock special decisions or national focus rewards. It can also be applied in AI strategic logic to evaluate actual casualty ratios in a given war, determining whether to trigger armistice or surrender events.
# Example: Poland unlocks a special decision when it inflicts over 200k casualties on Germany
GER = {
casualties_inflicted_by = {
opponent = POL
thousands > 200
}
}
Synergy
[casualties](/wiki/trigger/casualties) / [casualties_k](/wiki/trigger/casualties_k): Using these triggers together with casualties_inflicted_by allows you to check both "total own casualties" and "casualties inflicted on enemies" simultaneously, enabling calculation of bidirectional casualty ratios and constructing more comprehensive battle assessment conditions.
[has_defensive_war_with](/wiki/trigger/has_defensive_war_with): Commonly used as a precondition to confirm current defensive war status before using casualties_inflicted_by to determine whether the defending side inflicted sufficient cost on the invading nation, ideal for triggering "stubborn resistance" type events.
[any_enemy_country](/wiki/trigger/any_enemy_country): When nested with this trigger, allows iteration through all enemy nations to check whether at least one enemy nation suffered heavy casualties from your forces, suitable for multi-front war scenarios.
[country_event](/wiki/effect/country_event): After casualty conditions are met, triggers exclusive events as an effect—the most common "casualty milestone → event reward" chain pathway.
Common Pitfalls
- Confusion between scope and opponent direction: The scope of
casualties_inflicted_by is the receiving side (the nation sustaining casualties), while opponent is the inflicting side (the nation causing casualties). Beginners often reverse this, mistakenly assuming scope refers to "the side dealing casualties," resulting in the condition always evaluating to false.
- Overlooking the thousands unit: The field uses the "thousands" unit; writing
thousands > 200 represents 200,000 personnel. Directly entering 200000 will cause syntax or logic errors—unit conversion is essential.