Sandustry Automation Guide – Production Chains That Recover
Learn Sandustry automation from measured throughput to buffers, gates, modular layouts, restart tests, and fault-tolerant scaling.
Published 2026-08-21 · Updated 2026-08-21 · Early Access guidance
Model the chain before building
Write each transformation as input, condition, output, and unwanted state. For example: dry feed enters a controlled wetting zone; conditioned feed leaves; the next stage separates desired output from residue. The official sources confirm conveyors, filters, drones, pipes, pumps, and multistep production, but they do not publish stable universal rates. Use the calculator with rates observed in your current build. A model is useful even with imperfect numbers because it reveals missing destinations and feedback loops before they become physical blockages.
Measure a single module
Run one module for a fixed interval and count accepted output. Repeat after clearing the input and output buffers. If results differ, the process is sensitive to fill level, geometry, simulation state, or supply. Record a conservative rate rather than the best burst. Size the next stage from that conservative value. Community posts are valuable clues about where users struggle, especially wetting, pipe behavior, and material backflow, but they are not a substitute for measurement in your own save and version.
Buffer unstable boundaries
Falling pixels and fluids are bursty. A buffer between stages absorbs that variation and creates a diagnostic signal. It needs an inlet that cannot bury the outlet, an overflow below the contamination threshold, and enough visual access to see its state. Avoid one giant shared buffer for unrelated materials. A full upstream buffer indicates downstream restriction; an empty one indicates supply restriction. If both fluctuate wildly, increase observation time before changing capacity.
Control failure, not just flow
Design an off state for sand, water, heat, and power. The exact controllable blocks may change during Early Access, so verify control behavior in a small sandbox. A shutoff should fail safely: loss of power should not dump an entire reservoir, and loss of input should not let another material invade the empty lane. Put manual isolation points before expensive or destructive processes. Label them so recovery does not depend on remembering a hidden sequence.
Build modules with interfaces
A module has a defined feed height, output height, accepted material, maximum buffer line, and maintenance access. Leave one tile or corridor around boundaries where possible. Duplicate only after the module survives empty input, full output, pause/resume, and a save/reload check. Interfaces let you replace a wetting chamber or sifter without rebuilding the whole base. They also make community blueprint ideas safer: you can test a foreign module against a known input and quarantine its outputs.
Scale from evidence
When demand rises, inspect accumulation rather than guessing. Add parallel capacity to the constrained stage, then remeasure the complete chain. Do not multiply every stage at once. Track the update date beside observed rates, because a patch may invalidate them. Use the blueprint notebook to store layout assumptions and the sandbox checklist to rehearse changes. The strongest advanced factory is not the densest one; it is the one that exposes state, contains failure, and returns to production after interruption.
Sources and evidence notes
- Sandustry on Steam
Tier 1. Developer/publisher description, Early Access status, features, and requirements; checked 2026-08-21.
- Sandustry by Lantto
Tier 1. Developer overview of falling sand, automation, exploration, bosses, puzzles, and tech; demo-era mechanics are not treated as retail balance facts.
- Sandustry Steam discussions
Tier 4. Used to identify recurring questions and official support topics, not to establish universal mechanics.
- r/SandustryGame community
Tier 4. Used for demand signals and candidate failure modes; ratios and workarounds require in-game verification.