automation
How to Automate Red Sand with a Redweaver
Fresh Steam and Reddit discussions ask how to automate Red Sand and keep Voidbloom production supplied. The official Redweaver and Redsand pages establish a reliable answer boundary: Redweavers create a Redsand trail, can be captured and released, and eventually stop if they enclose themselves. Those facts support a recoverable production bay, but they do not prove an exact room size, guaranteed turn pattern or universal pixels-per-minute rate.
Early Access v0.5.6 · mechanics checked 2026-09-06 · Checked 2026-09-06
Find and capture a Redweaver
The current official Redweaver page identifies it as a wild critter that can be captured with a Corraller and released elsewhere. That makes the animal—not a hidden crafting recipe—the confirmed renewable production component. Prepare the destination before capture so the critter is not released into an active mixed-material factory.
Use a small manual trial and preserve access to the Corraller. This guide does not provide a fixed map coordinate because public evidence does not establish one universal spawn location for every save. Search accessible terrain, identify the critter by its current in-game name, and avoid treating a community screenshot as a coordinate.
Build an empty, serviceable walking bay
Release the Redweaver into a dedicated bay with visible floor space, a boundary and a way to recapture it. The official page says it travels in straight lines for a time and then turns. The practical goal is not a perfect loop; it is enough open movement to leave a trail while keeping every section reachable.
Start larger than the animal's immediate footprint, but do not publish or trust one magic dimension. Observe your current build, note where turns happen, and keep unrelated liquids, flowers and wisps outside. A clean bay makes Redsand production and blockage obvious.
Understand why production stops
A moving Redweaver produces Redsand in its trail. The same official page warns that it can box itself in with that material and then stop producing. A motionless animal surrounded by red material is therefore a documented maintenance state, not proof that the creature has permanently run out.
Pause downstream demand and remove only enough trail to restore a route. Avoid firing weapons or deploying uncontrolled excavation near a valuable captured critter. If movement does not resume, recapture it with the Corraller, clear the bay, and recommission a small test.
Collect the trail without blocking the animal
Place collection at the edge or below a tested route so extraction does not become another wall. The official Redsand page classifies the output as a solid, so normal solid-material handling concepts apply, but the exact collector geometry is a layout choice rather than a documented universal blueprint.
Watch one full movement-and-turn cycle before adding continuous belts, portals or logic. If the output lane fills, stop accepting more Void Petals or other downstream ingredients and clear collection first. Production that cannot shut down will eventually recreate the same box-in failure.
Deliver Redsand to the Voidbloom contact lane
The confirmed late-game use is combining Redsand with Void Petals. The official Redsand and Void Petal pages say the pixels must fall vertically onto one another. Pushing the materials together from the side with conveyor belts does not force the conversion.
Build a narrow, visible drop point with one ingredient above the other and test a small batch. Keep spare Redsand out of the walking bay's exit so a downstream backup cannot grow backward and trap the Redweaver.
Separate source automation from conversion automation
Treat the Redweaver bay, Redsand storage and vertical Voidbloom contact as three modules. Confirm trail production first, then reliable extraction, then the material reaction. Combining all three in the first build makes a stopped animal look like a failed recipe and a full reactor look like a capture problem.
Put an inspection gap or limited buffer between modules. A correct Redsand source may still feed no Voidbloom if petals approach sideways, while a correct contact lane may starve because the walking bay has boxed in.
Add a safe reset procedure
A recoverable bay needs four actions: stop downstream draw, recapture or isolate the Redweaver, clear accumulated Redsand, and release the critter into an open route. Test this reset before scaling. Preserve nearby structures and avoid clearing an entire production floor when one blocked path is enough.
Current community posts discuss automatic destruction and several critter layouts, but they do not establish one safe permanent method. Treat destructive automation as experimental until it repeatedly avoids harming the creature, preserves output and recovers after a full buffer.
Measure your build without promising a rate
Count useful Redsand reaching the buffer over several observed cycles, including turns and one near-full condition. That is a measurement for your save and geometry, not a game-wide rate. Expand only when the current bay's output is the first verified bottleneck in the Voidbloom chain.
If production differs after a patch, recheck the official Redweaver and Redsand pages before changing the guide. Record the build, bay shape, material depth and whether recapture restores movement. Those details can turn a one-off report into evidence without inventing a best layout.
Sources and evidence notes
- Redweaver — Sandustry Official Wiki ↗
Tier 1 · Publisher-hosted Early Access critter page. Corraller capture and release, Redsand trail production, straight-line movement, turning behavior, and self-boxing failure mode
- Redsand — Sandustry Official Wiki ↗
Tier 1 · Publisher-hosted Early Access material page. Redsoil origin, solid behavior, Void Petal conversion, and required vertical contact for Voidbloom
- Void Petal — Sandustry Official Wiki ↗
Tier 1 · Publisher-hosted Early Access material page. Void Flower Soil output, Planter Box permeability, Wisp behavior, and vertical-contact processing
- Void petal automation — r/SandustryGame ↗
Tier 4 · Current Early Access automation discussion. Player demand for continuous Voidbloom input and a community pointer to Redweavers as a Redsand source
- Sandustry Steam discussions ↗
Tier 4 · Mixed Early Access community reports. Recurring questions and candidate failure modes only, including current Aura saturation, Steam Dryer, Red Sand automation, co-op, puzzle, Water, and late-game performance topics