Automated Area Defense Planner
PROTECT AN AREA creates a deterministic, budget-constrained defense proposal for a user-drawn region. The protected area is only a label and polygon: it is not resolved to a country, and no domestic supplier is added automatically.
Planner Workflow
- Open Build → PROTECT AN AREA.
- Enter an area name and draw either a box or free polygon on the map.
- Select every supplier country the planner is allowed to use.
- Select Anti-air, Anti-drone, Jammers, or all three roles.
- Enter the total procurement budget in millions of USD.
- Adjust the role sliders. They automatically rebalance to exactly 100%.
- Choose Generate Preview, inspect the proposal, then use Back / Edit or Deploy Plan.
Suppliers and Catalog Availability
Every supplier must be selected explicitly. The supplier list contains only countries represented by reviewed defense platforms in the current catalog. Joint systems are eligible when either participating supplier is selected. For example, a France-Italy system may be considered when France or Italy is allowed.
Defense Roles and Real Capabilities
Anti-air remains threat-aware across aircraft, cruise missiles, ballistic missiles, hypersonic threats, bombs, artillery, and other missiles. Anti-drone uses reviewed drone-interception or counter-UAV gun capabilities. EW coverage remains separate for GNSS, datalink, communications, radar, and drone-related effects.
A multifunction system has one assigned spending role but keeps all of its reviewed capabilities in the coverage analysis. It is purchased and charged only once.
Budget and Allocation
Role percentages are soft spending targets. The planner must remain within the total budget and represent every selected role, but it may deviate from the requested split to produce a useful plan. After broad coverage and capability diversity, it adds meaningful capacity and resilience toward at least 90% budget utilization when the selected catalog supports it. Preview explains when catalog limits or remaining funds prevent further useful purchases.
How Locations Are Chosen
The planner combines uniform land points with weighted cities, security and military-related sites, military transport infrastructure, and civilian transport infrastructure. Population weighting is capped so one large city cannot dominate the whole plan.
It first seeks new weighted geographic coverage, then improves capability and layer diversity, and finally adds launcher depth at important locations when new placements offer little additional coverage.
Understanding the Preview
The preview shows temporary markers and capability-specific range layers, requested and actual spending, selected systems, launcher counts, geographic and priority-site coverage, threat-class coverage, EW-effect coverage, and points protected by multiple sites. Preview generation does not alter platforms, defenses, camps, targets, or saved deployments.
Deploying the Plan
Deployment requires explicit confirmation. The server independently revalidates the polygon, suppliers, roles, templates, launcher limits, coordinates, and authoritative costs before making changes. A successful deployment adds the new area and defenses to the current workspace; existing platforms, defenses, camps, targets, and protected areas remain.
The insertion is atomic: if validation or insertion fails, the transaction rolls back and the existing workspace remains intact. A loaded deployment remains linked and is marked modified so Update Loaded can save the addition.
Saved Boundaries and Moving Defenses
The named protected-area boundary is saved automatically with the active workspace. Signed-in users keep it under their Google account; guests keep it for their current browser session. The purple boundary is visible by default and can be shown or hidden from Layers → Protected areas.
Layers → Protected areas lists every area with its current linked count, outside count, and authoritative procurement spend. There is no application limit on how many areas may be added, including overlapping areas. Hovering the map label shows current spend; use Zoom or Details to inspect an area, Edit to rename or redraw that specific area, Delete to remove its boundary, or Protect another area to keep building the workspace.
Select the boundary to review current procurement spend, geographic, priority-site, capability, and layer-depth estimates. Moving, editing, or deleting a linked defense refreshes these estimates. A boundary does not automatically move with its defenses, but its name and polygon can be edited at any time. A linked system outside it is clearly identified and still contributes wherever its reviewed range reaches planning points inside the area.
When manually placed air defenses are inside a boundary, Update Area appears. It adds those systems without removing prior links. A defense may support multiple overlapping protected areas.
Deleting a protected area removes only that area and its defense relationships. The linked defense platforms remain in the workspace and may be attached to another area later.
Normal deployment Save and Update operations include protected areas. Loading, combining, copying, or sharing a deployment restores the named boundaries and their links to generated defenses.