Direct answer: Build a Dust Front RTS base around a readable resource-to-production flow, protected critical structures and clear reinforcement routes. Resilience is more useful than a perfectly compact footprint.
Start from functions
Official material names base construction, mining, processing, factories, barracks, storage and defenses. Begin by grouping buildings by function: extraction, conversion, production, storage, command and protection. This makes the layout legible and exposes a missing link before the base grows.
The current public information does not establish every building's footprint or prerequisite. Use the live build to record those details, and keep this guide focused on layout principles that remain valid while the list changes.
Protect the chain
Place the structures that keep resources moving where they can be defended and repaired. A decorative perimeter is not a substitute for protecting the input and processing stages that supply the entire base. Consider which building loss would stop production first, then give it space and a response route.
Avoid stacking every essential function into one dense block. Compactness can reduce walking or travel time, but a single attack should not disable extraction, storage and every factory at once.
Keep routes open
Leave movement space between important groups. Reinforcements need a predictable path to the threatened side, and damaged structures need access for recovery if the current build supports repair behavior. Use the map's natural cover or edges only after confirming they do not trap production or movement.
Mark a primary and secondary route. If the first route becomes unsafe, the second should still connect the core economy to the defensive line.
Add production in layers
Do not build every factory as soon as it is unlocked. Establish one dependable production link, test its input demand and then add capacity when the economy can feed it. Multiple idle factories create the appearance of progress without increasing useful output.
Layering also improves recovery. If the forward line is lost, the core can continue to produce a replacement force instead of rebuilding every function at once.
Defend the decision points
Defense should be placed where it changes the enemy's route or buys time for a response. Protect exposed extraction, processing entrances and the approach to production. A defense that cannot be supported or repaired is an expensive object, not a resilient base.
Current defensive values and building names require version-specific confirmation. Record what a structure actually stops, how long it holds and which route it protects before calling it optimal.
Expansion footprint
Expansion should add a capability, not only territory. Before placing a new cluster, know what resource or production function it serves and how the main base supports it. Keep a fallback connection or reserve so losing the extension does not collapse the core.
When the global map or garrison systems are available in a public build, add those effects to the layout notes. Until then, keep them marked as unconfirmed rather than assuming the store-page description represents the Demo.
Base review checklist
- Can you identify the input-to-output flow at a glance?
- Can a small attack disable every critical function?
- Is there a safe route for units and a fallback route?
- Are production queues supported by the economy?
- Can the core recover after losing an extension?
- Are defense recommendations tied to observed behavior and version?