Skip to content
Find The NeedleSteam Demo · factory notes

Factory setup

Connect multiple pumps and pulpers to one water network

Demo V42 player layout · thread rechecked October 8, 2026

The short answer

Put a splitter at every point where a machine feeds water into, or takes water out of, the shared network. That is the method Atrophus described and illustrated for multiple producers and users in Demo V42.

Give each pump and each pulper its own connection to the common pipe run. A connected network is not a guarantee that your pumps can run every pulper at full speed.

On this page

Before you change the pipes

This guide starts after you can place pumps, pulpers, pipes and splitters. It does not explain their unlock order. Check the Demo build displayed in your game: the reference layout says V42. Later builds may change pipe placement or connections.

Identify each pump's water outlet and each pulper's water intake. Keep the water route separate from your hay belts and power connections while planning it. The original problem was joining multiple feeds and choosing the pulper intake side, so account for the ports' actual positions before laying the common run.

Read the shared-network diagram

Pump A and Pump B each connect through their own splitter to the shared water line. Pulper A and Pulper B each take water through a separate splitter.
Original relationship diagram based on Atrophus's V42 example. Lines show which connections belong together; positions and colors are not an in-game blueprint or proof of the splitter's port orientation.

The repeated part matters: pump → its splitter → common pipe run; common pipe run → a separate splitter → each pulper. This drawing does not specify tile spacing, pipe shape, upgrade level or flow rate. Use the actual connector sides shown in your build.

Connect sources and users one at a time

  1. Start with the first source. Place a splitter at the pump's connection to the network, and join it to the shared pipe run.
  2. Add the next pump through another splitter. Do not treat the coupler as an undocumented universal joiner. The successful example uses a splitter at each machine connection.
  3. Branch to the first pulper through its own splitter. Route that connection to the pulper's actual intake. Do the same for the next pulper.
  4. Inspect every machine connection. Trace each source and user back to the common run. An omitted connection-point splitter is the first difference to check against this method.
  5. Check production separately. Compare how each pulper runs after the change. If the piping is connected but production is still low, move to the supply checks below rather than assuming more connectors provide more water.

Connected does not mean enough water

Wragon reported that one pump with fully upgraded machines supplied two pulpers at only 92%. That report does not establish the capacity of every upgrade combination, and Atrophus's picture does not provide a measured load test.

The shared-network method lets multiple sources and users connect; it does not give an optimal pump-to-pulper ratio. Inspect your own machine indicators and compare one pulper with the combined load. This comparison is a diagnostic suggestion, not a measured fix for the reported 92% result.

Record pump count, pulper count and their upgrade levels before changing one factor. Do not copy an older video's liters-per-second number into a V42 calculation, or buy upgrades expecting this page to guarantee 100% throughput.

If a pipe angle will not connect

Beertruck reported trouble after an October 4 patch and said 90° connections had worked beforehand. That reply did not identify its build. It is a separate failure report, not proof that all V42 networks fail or that the issue has been fixed.

A later reply from GameOverRIP suggests pressing H to change shapes. If your build offers that control, inspect the available shape while placing the connector. The reply does not demonstrate that H repairs the 90° issue.

If the connection still fails, keep the successful network rule and the placement problem separate. Capture the build number, the machine port and the failed angle for a reply in the original discussion. Repeatedly rebuilding the whole factory is not a proven repair; the original poster also reported accidentally removing a machine while trying to remove a pipe.

Do later placement complaints change the connection rule?

In the October 1 Reddit water discussion, Ogrehunter reports awkward pulper water-port placement. turtlrpups describes using one pump for each pulper and finding expansion frustrating. Neither provides a build number or measured capacity test.

That personal one-to-one setup does not establish a connection limit or invalidate Atrophus's V42 shared-network example. Use the V42 rule within its stated scope, check your own machine ports, and treat unresolved placement or capacity problems separately.

Check the result before expanding

  • Each producer and each user has a splitter at its connection to the network.
  • Every machine's water port joins the intended common pipe run.
  • Pulper behavior is checked under your real load, rather than inferred from the topology.
  • Any failed angle is recorded with a build number. A T junction or water buffer requested by players is not assumed to exist.

Sources & version

Community instructions, not our own gameplay test. Version-specific advice may change after a Demo update.

Keep going

Your next useful guide

Place scanners before hay is sold or burned →Route loose hay through scanners, check every branch, and distinguish needle-loss warnings from unproven recovery claims.Change the Demo back to English on Windows →Use the reported settings.cfg locale value when an unreadable game menu blocks you, while keeping the original file and saves intact.Does the Dispatch timer limit a Demo run? →The October 5–6 player explanation of the Dispatch clock, its reported reset behavior and what it does not establish about the full game.Buy upgrades when double-clicking does nothing →Use the right-pane Buy button in the Demo upgrade screen, with the Linux player confirmation and checks for a purchase that still fails.Stop an unwanted belt exit or splitter output →Two reported Demo methods: reverse a short end section or close a Smart Splitter output, with checks for bypasses and backed-up input.Diagnose the SSE4.2 CPU error at Demo startup →Check whether Windows exposes SSE4.2 to the Demo and distinguish a CPU instruction requirement from graphics, language or save problems.Try a reversible OpenGL launch test for graphics crashes →Apply the community-proposed Godot compatibility flags in Steam, test the result and restore your original launch options if they do not help.