The systems of recovery.

A loss should create a decision

Fortress defense is built around pressure. But pressure becomes more interesting when the player can do more than replace whatever was destroyed. October’s design work made recovery a central part of Rampart Zero.

Repair Bays, Engineers, salvage, research, and servicing connect the aftermath of one wave to preparation for the next. Spend on a replacement force, recover an existing vehicle, or invest in a capability that will change the next fight: each choice draws on the same limited resources.

Autonomy supports intention

An Engineer can recover salvage and repair vehicles. Damaged forces can withdraw to powered service infrastructure and later return to their assignments. Movement and queue handling matter because a theoretically useful service system fails if its vehicles block one another.

These behaviors reduce repetitive supervision while preserving player authority. A direct order takes priority. The purpose is to make the army competent enough to carry out your strategy, not to make the strategy for you.

The support network is part of the battle

Aircraft have finite sortie ammunition and return to Airfields for rearming. Shields draw power. Research competes with present-day military needs. Losing infrastructure therefore changes what the army can sustain.

This creates decisions across different timescales: respond to a threat now, preserve a wounded unit, keep the power network working, and build toward the next capability. A strong base is a set of relationships rather than a collection of expensive objects.

Beyond the feature checklist

The implemented campaign spans fifteen waves and a Titan encounter, with endless play available afterward. That structure gives progression a destination, but it does not settle balance or onboarding.

The development history is candid about what remains: full-run testing, readable threats, a comprehensible first session, and evidence that players want to return. These questions guide the private playtest. Finishing a system is the beginning of learning whether it serves the game.

Boundaries make autonomy useful

A player order takes precedence over an automatic repair trip. Engineers respect explicit assignments. Repair sources do not add unlimited throughput by stacking on one vehicle. Salvage returns materials from wrecks rather than resurrecting destroyed units.

Airfield servicing consumes time and power; the design does not introduce a separate fuel economy. Carrier flights stay connected to a vulnerable home unit and a bounded replacement budget. These rules keep logistics understandable while giving infrastructure a meaningful role.

The Commander and ordinary unit autonomy solve different problems. Language can express a plan, while deterministic field behavior handles the repeated work of reaching a destination, avoiding a blockage, queuing for service, and returning to an assignment. Neither layer should wrest control away from the player.