automation
Sandustry Wet Seed Automation That Can Recover
Current players report that seed wetting becomes the Flower line's first high-volume bottleneck. This page separates official material behavior from community layout candidates and gives each design a shutdown and recovery path.
Early Access · checked 2026-08-27 · Checked 2026-08-27
Understand why Wet Seeds stall
Dry Seed becomes Wet Seed on contact with Water. The official page says Wet Seed shares Water's density and can remain suspended. A deep tank therefore stores product throughout its volume instead of delivering everything neatly to the bottom.
The same page says Wet Seeds are less dense than dry Seeds, creating a separation clue. Observe where each state accumulates before choosing a transport method.
Build a small visible wash chamber
Use limited Water with a marked normal level, an accessible dry-seed input and a separate Wet Seed outlet. Keep the chamber away from the only Water reserve. Feed a small batch and confirm conversion before installing a continuous line.
A current player report says Water-level neglect clogged an otherwise useful build. Treat level control and overflow as part of the machine, not optional decoration.
Choose one transport pattern
Current players report three plausible patterns: introduce dry Seed near the bottom and collect floating Wet Seed above; use Clearing Frames or Launchers to move suspended product toward an outlet; or use a shallow filtered lane that keeps the feed one pixel high. These are community-tested candidates, not official blueprints.
Choose one pattern and record the expected route. Combining portals, launchers, deep tanks and several filters in the first test makes failures impossible to locate.
Recycle dry Seed
Put an inspection point after the chamber. Any dry Seed that passes without converting should return to the wash input, while confirmed Wet Seed continues to Planter Boxes. Keep the return loop visible and capacity-limited.
Do not let recycled Seed form an unlimited closed pile. If Water runs out, stop new dry input before the loop fills every interface.
Avoid state-change jams inside Filters
The official Filter page warns that a material changing state while passing through a Filter can become stuck. Seed turning into Wet Seed at the Filter boundary is a documented example. Keep the main wetting contact inside the chamber, then filter after the state is observable.
When a boundary jams, stop Seed and Water, remove the smallest trapped sample and restart with one layer. Do not widen input until the clean lane survives an empty-Water test.
Scale with parallel lanes
One current discussion recommends small complete vertical modules rather than a single oversized production unit. Copy a lane only after it survives high Water, low Water, dry-seed leakage, full Wet Seed output and reload.
Parallel lanes isolate failure and make throughput measurable. A larger tank can hide inventory while still starving every Planter Box.
Diagnose by visible state
Dry Seed everywhere: restore Water contact or recycle. Wet Seed suspended: improve directed transport rather than adding more input. Water escaping: lower the operating line and add drainage. Outlet full: stop the upstream Seed feed before clearing.
After recovery, restart with a limited batch and watch the first converted Seeds reach the Planter Box. That is the closed loop; an active launcher alone is not proof of useful output.
Sources and evidence notes
- Wet Seed — Sandustry Official Wiki ↗
Tier 1 · Publisher-hosted Early Access material page. Seed plus Water conversion, Wet Seed density, suspension behavior, and Planter Box use
- Filter — Sandustry Official Wiki ↗
Tier 1 · Publisher-hosted Early Access building page. Allow/Block behavior, density limits, state-change jams, and exit requirements
- Research — Sandustry Official Wiki ↗
Tier 1 · Publisher-hosted Early Access research reference. Current tiered research names, costs, dependencies, and Tier 5 unlock contents
- Having trouble automating seed wetting — r/SandustryGame ↗
Tier 4 · Current Early Access player discussion. High-volume bottlenecks, water-level failures, recycle patterns, and candidate layouts