Hands-On Usage
This trigger is commonly used to check whether a particular theater has accumulated sufficient air power—for example, validating in custom decisions or national focuses whether the player has completed air superiority deployment to a specific region. Typical scenarios include: triggering "air superiority achieved" type achievements, or restricting certain strategic decisions from being available when air power is insufficient.
# Example: Allow a decision to activate only when sufficient aircraft are stationed in designated regions
available = {
num_planes_stationed_in_regions = {
value > 200
regions = { 18 47 }
}
}
Synergy
[has_deployed_air_force_size](/wiki/trigger/has_deployed_air_force_size): Serves as a complementary check—the former evaluates base-stationed aircraft in specific regions, while the latter assesses total nationwide deployment scale; combining both enables a dual-threshold implementation of "globally sufficient and locally robust."
[divisions_in_border_state](/wiki/trigger/divisions_in_border_state): In air-ground coordination scenarios, commonly paired with this trigger to ensure the target direction simultaneously possesses both ground forces and air cover before offensive decisions are allowed to trigger.
[controls_state](/wiki/trigger/controls_state): Typically requires first confirming your control over specific states before checking stationed aircraft counts to avoid false readings on base data in uncontrolled territories.
[activate_targeted_decision](/wiki/effect/activate_targeted_decision): When stationed aircraft meet the condition threshold, use this effect to activate decisions targeting specific objectives—the most common downstream action of this trigger.
Common Pitfalls
- Conflating "stationed" with "deployed":
num_planes_stationed_in_regions counts aircraft that have airbases in that region, not aircraft currently executing missions there. When aircraft are reassigned to other regions for operations, they remain counted as long as their home base remains in the specified region—newcomers often mistakenly believe this reflects real-time combat positioning.
- Incorrect region ID input: The
regions field expects strategic region numeric IDs, not state IDs. Though their numeric ranges may overlap, they carry different meanings; directly entering a state ID will result in the condition never triggering or matching the wrong region.