Hands-On Usage
has_bombing_war_support is commonly used in strategic bombing-related mod scenarios, such as determining when a nation's war support drops to a dangerous threshold due to bombing damage, triggering diplomatic surrender options or activating specific national focuses/decisions. Typical use cases include: when the war support penalty from bombing exceeds a certain threshold, allowing players to unlock a "seek armistice" decision, or triggering AI surrender logic.
# Open armistice decision when bombing causes significant war support penalty
available = {
has_bombing_war_support > 0.3 # Bombing penalty exceeds 30%
has_war = yes
}
Synergy
[has_casualties_war_support](/wiki/trigger/has_casualties_war_support): Both represent negative sources of war support (bombing vs casualties), typically stacked together to evaluate whether a nation's overall war support has been severely damaged by multiple factors.
[has_convoys_war_support](/wiki/trigger/has_convoys_war_support): Convoy losses also generate war support penalties, and using them alongside bombing penalties constructs a comprehensive "total war pressure" assessment condition.
[add_war_support](/wiki/effect/add_war_support): After condition triggers are met, use this effect to directly compensate or further reduce war support, forming a complete logic loop of "reach bombing penalty threshold → compensate/penalize".
[add_political_power](/wiki/effect/add_political_power): When bombing pressure reaches critical levels, pair it with granting political power to simulate the domestic political cost of a government seeking diplomatic solutions under bombing pressure.
Common Pitfalls
- Reversed comparison logic: This value represents "negative penalty amount"—larger values indicate more severe war support damage. Beginners often mistakenly think smaller values mean "more bombed"; actually, you should use
> to filter cases of severe damage, not < (unless intentionally filtering nations with minimal bombing impact).
- Forgetting scope must be COUNTRY: This trigger only works in country scope. Placing it in state scope (such as within
limit blocks in state-level loops) causes script errors or silent failure. Ensure the outer scope has switched back to country level.