Repository navigation
Steam Networks and Tanks
Steam is a typed network resource, not a bucket fluid. Brass steam pipes, compatible machines and steam track connect it. Touching machines can conduct onward. Distribution is every eight game ticks; no steam is lost simply because a pipe run is long.
basesteam:steam_tank is a 10,000-unit reserve:
- It requests steam at backup priority, so active loads can be supplied first.
- It releases stored steam to higher-priority consumers when needed.
- A redstone signal disables its output.
- Its stored steam undergoes local decay: 0.0625 per game tick, about 1.25 per second at 20 TPS.
Use it to smooth temporary shortages, store boiler surplus or run through a short interruption. It is not a pressure booster, repeater or generator. Installing tanks every few blocks does not counter distance loss, because the pipe system has none. Extra tanks increase capacity but also add their own storage decay.
| Component | Instruction |
|---|---|
steam_pipe |
Connect the loaded steam network; no per-block loss. |
steam_switch |
No redstone = conducts; redstone = disconnected. |
steam_track |
Pipe plus steel frame; supports drill movement while carrying steam. |
Unloaded pipe sections do not keep chunks loaded or bridge across unloaded terrain. Supply can resume when the relevant sections load again.
The gauge shows that machine's local buffer, not a single pressure value shared by every connected block. Steam-consuming machines using the common decay routine lose 0.0625 steam per tick locally; that is not a pipe-distance penalty.
A low reading under load can mean supply is being spent immediately. A spinning bit alone does not prove ongoing mining. Check new output, remaining fuel/water and behaviour with the load isolated. If one machine differs persistently after a full restart, record the layout and readings before breaking pipes.
John's maintained 1.10.2 field-test layout, 13 July 2026; not original gallery artwork. Credits.