30-second source-to-destination check

  1. Source

    Confirm that supported non-Lava liquid is still present and can touch the Pump.

  2. Pump

    Place it over a Pipe tile. Let liquid touch any part of the Pump and clear non-liquid pixels from inside it.

  3. Pipe

    Start or end each extension on an existing Pipe tile. A nearby stroke or crossing is not automatically a join.

  4. Liquid Vent

    Confirm it belongs to the intended Pipe network; the official Vent page does not specify every adjacent placement shape.

  5. Destination

    Leave room for released liquid: a Vent stops once three-quarters of it are submerged.

If the transport line works but the source keeps shrinking, return to the ordinary Water source and containment checks. For Lumlings, Cryoblaster Snow, Rain, delayed buffers, or reload failures, use the separate Infinite Water supply and stability test. If the Pump, Pipe, or Liquid Vent is not available yet, confirm the Fluids unlock in the Research order guide before rebuilding the network.

Why is my Sandustry Pump not working?

The current official Pump page says every pixel of the 4 × 4 Pump can take in liquid; when fully submerged, it can feed up to 16 liquid pixels per tick. Place the Pump on top of a Pipe tile. It is non-solid, so non-liquid material inside it can stop transport. Clear that material and let the intended non-Lava liquid touch the Pump before retesting.

Why does the Pipe look connected but move nothing?

Update #4 changed Pipe construction in v0.5.7: Pipe strokes placed next to each other no longer connect automatically. To extend a network, start or end the new stroke on an existing Pipe tile. Drawing across another Pipe line creates a Pipe Bridge; do not diagnose it as a joined network merely because the lines cross. Use Pipe mode to trace the actual route. The current Pump page confirms placement over a Pipe, while the Vent page requires a network connection without defining every adjacent placement shape.

Use the v0.5.7 Pipe construction rule before rebuilding a network.
What you seeOfficial ruleCheck
Two Pipe strokes touch side by sideAdjacency alone does not join newly built strokes.Start or end an extension on an existing Pipe tile.
One Pipe line crosses anotherDrawing over a crossing line creates a Pipe Bridge.Trace each route in Pipe mode; do not assume the crossing joins them.
Pump sits near a PipeThe Pump page documents placing it on top of a Pipe.Place the Pump over a Pipe tile, then check liquid contact.

Why does the Liquid Vent stop outputting?

The current official Liquid Vent page gives a maximum output of 4 liquid pixels per tick. It says the Vent stops when three-quarters of its 4 × 4 body are submerged, leaving only the top row above the liquid. Lower the destination level or move the Vent higher before rebuilding the Pipe. A fully submerged Pump and four Vents match the published maximum rates, but that is a capacity ceiling, not a guaranteed layout result.

Liquid transport diagnostic: Pump placed on a Pipe, extensions joined at an existing tile, crossings bridged, and Vent kept below its submersion limit.
Check source contact, deliberate Pipe joins, Bridge crossings, and Vent submersion before adding branches.

Why does the system work and then stop?

Recheck both changing ends: the source can stop touching the Pump, non-liquid material can enter it, or rising liquid can submerge three-quarters of the Vent. A connected Pipe does not create Water and cannot keep a submerged Vent releasing it.

Why does the wrong liquid reach the output?

The official Pipe page allows multiple Pumps and Vents on a connected network and says mixed supported liquids distribute across its outputs. Keep each liquid on a separate network when the destination must stay pure; a v0.5.7 Pipe Bridge crossing alone does not join them. Lava is explicitly excluded. Steam is a gas, and current official Pipe documentation does not establish Steam transport through this liquid network; do not copy a Demo-era Steam reply as a current rule.

Still not working? Match the endpoint or network symptom.
SymptomLikely causeCheck and fix
Pump does not take WaterWater does not touch the Pump, non-liquid material is inside it, or it is not on a Pipe.Clear the Pump, place it over a Pipe tile, and expose it to Water.
Pipe looks connected but nothing movesAdjacent strokes are separate, a crossing is a Bridge, or an endpoint is disconnected.Start or end a new stroke on an existing Pipe tile; trace the actual route.
Liquid Vent never releasesIt is disconnected or three-quarters submerged.Confirm the network and lower the destination level.
System stops after runningSource contact ended or the destination submerged the Vent.Inspect both ends before replacing Pipes.
Wrong liquid outputMixed liquids share a network.Separate networks by liquid.

Update record

  • 2026-10-07 — Added official v0.5.7 Pipe joins and Bridges; corrected current Pump intake, Vent submersion, and maximum-rate descriptions.
  • 2026-08-24 — Retargeted the page to Pump-not-working language and clarified Water supply, renewable supply, and transport boundaries.
  • 2026-08-23 — Added the five exact symptom anchors, source-to-destination check, and endpoint-placement conflict.
  • 2026-08-22 — Published the initial three-stage fluid diagnostic.

Frequently asked questions

Why is my Sandustry Pump not working?

The current official Pump page says every pixel can take in liquid. Place the Pump over a Pipe tile, let non-Lava liquid touch it, and clear non-liquid material from inside the Pump.

Why does the Pipe look connected but move nothing?

Since v0.5.7, adjacent Pipe strokes do not join automatically. Start or end an extension on an existing Pipe tile; crossing another line creates a Pipe Bridge, not a junction.

Why does the Liquid Vent stop outputting?

The current official Vent page says it stops releasing liquid when three-quarters of it are submerged. Lower the destination level or move the Vent above it, then retest the connection.