Direct answer: Use Dust Front RTS factories to answer a defined battlefield need, and keep queues short enough that extraction and processing can sustain them. When production stops, diagnose the upstream input before adding capacity.

What is confirmed

The official description references factories, mineral processing, vehicle production and military equipment. It does not provide a complete public table of factory types, production times or resource costs. This page therefore focuses on queue behavior and verification rather than invented numbers.

Open each production menu in the current build and record the exact categories, prerequisites and input icons. Mark each finding with the Demo version or date so future changes are easy to trace.

Give every queue a purpose

A queue should solve a current problem: protect the resource chain, create a mobile response, replace losses or prepare for a known objective. Filling it because capacity is available can consume the inputs needed for an emergency response.

Start with a small order, observe the result and extend it once the economy proves stable. The right queue length depends on mission pressure and replacement time, not a universal number.

Trace a stall backward

When a factory stops, inspect the chain in reverse order. Is the required processed material present? Is storage full or disconnected? Is another queue consuming the same input? Did a raid interrupt extraction or processing? This diagnosis is more reliable than building another factory immediately.

Write down the first stage that failed, not merely the final error message. The first failed stage is usually where the correction belongs.

Separate replacement from projection

Maintain enough capacity to replace a force that is already in the field. Only then commit spare capacity to a projected push or optional unit category. A plan that cannot replace one bad engagement is fragile, even if the first attack succeeds.

Mixed infantry, vehicle and aviation forces are part of the public game's described scope. Exact unit availability in the Demo must be checked before assigning a queue to a named class.

Build factory redundancy carefully

Redundancy can protect output when one facility is lost, but it also increases input demand and defense requirements. Add a second factory when the current queue is the operational bottleneck and the economy can maintain both. If the real problem is processing or storage, redundancy simply makes the stall more expensive.

Keep critical factories within a practical defense and reinforcement pattern. Production that cannot be protected becomes a recurring replacement cost.

Document version-sensitive data

When you publish costs, time or prerequisites, include the build identifier, date and source. Prefer an in-game screenshot or official update to a copied community table. If a value changes, keep a short version note instead of silently replacing the old recommendation.

Queue checklist

  • What mission need does this queue answer?
  • Which input is likely to become the bottleneck?
  • Can the economy replace the units after one failed engagement?
  • Is the factory reachable and defensible?
  • Does a second facility solve the real problem?
  • Are current values supported by a dated source?