Hands-On Usage
num_nukes_being_dropped is commonly used in nuclear warfare-related events or decisions to detect whether nuclear warheads are currently in a ready-to-drop state, thereby triggering special diplomatic penalties, war support changes, or AI reaction logic. For example, in a "Global Nuclear Panic" mod, you can use it to determine whether an emergency sanctions decision should be activated:
# In the available block of a decision
available = {
FROM = {
num_nukes_being_dropped > 0
}
}
Synergy
[has_nuclear_bombs](/wiki/trigger/has_nuclear_bombs) (the corresponding nuclear stockpile trigger in the whitelist does not exist, use instead) [add_nuclear_bombs](/wiki/effect/add_nuclear_bombs): When confirming that nuclear warheads are being dropped, you can use this effect to replenish nuclear reserves for relevant parties, implementing "nuclear arms race" logic.
[add_war_support](/wiki/effect/add_war_support): When detecting nuclear warheads being dropped, dynamically adjust war support for the target nation or your own side to simulate the morale impact of nuclear strikes.
[add_named_threat](/wiki/effect/add_named_threat): Use in conjunction to convert the current nuclear drop action into increased global threat values, enhancing the simulation of international diplomatic pressure.
[has_defensive_war](/wiki/trigger/has_defensive_war): Commonly combined with this trigger to determine the extreme situation of "simultaneously under nuclear attack while in a defensive war state," triggering special story events.
Common Pitfalls
- Misinterpreting the meaning of "ready to be dropped": This trigger counts the number of nuclear warheads currently ready and pending deployment, not warheads that have already detonated or struck their targets. Beginners often confuse this with nuclear stockpile quantity, leading to incorrect condition evaluation timing.
- Scope usage errors: This trigger is only valid under the
COUNTRY scope. If accidentally written within the limit block of a STATE scope, the game will not report an error but the condition will never evaluate correctly, making it difficult to detect during debugging.