Sandustry Snowmaker Guide: Water, Energy and Snow

Understand the machine's job before placing it

The Snowmaker converts liquid Water into a solid thermal material. It is useful wherever Snow supports cooling, storage, or a later state-change chain. Because the documented material ratio is one-to-one in pixel count, unexpected loss usually belongs to transport, output clearance, or observation boundaries rather than the stated machine conversion.

Power is a separate requirement. Four Water pixels at the intake do not complete an operation without Energy. Commission the machine with a small connected battery so one Energy change is visible, then move it to the broader grid after both inputs and the Snow output are confirmed.

Follow the documented input and output rules

The official page states that four Water pixels on top of the Snowmaker become four Snow pixels and consume one Energy per operation. Supply Water to the correct face and keep the four-pixel batch together long enough to trigger. A thin intermittent trickle can make the machine look slow while it waits for the complete input.

Snow is a solid output that needs clear space and follows material physics after creation. If it accumulates against the building, later operations can stop or send material into an unintended pocket. Give it a dedicated collection surface before attaching a heat or launch stage.

Build a serviceable layout

Build a small Water header above the Snowmaker, a visible Snow collection area below or beside the documented output, and an Energy connection that can be inspected. Add a fluid shutoff before the header so a repair does not release the entire Water reserve.

For a circulation experiment, keep the Snowmaker, heating step, Steam path, Condenser, and returned Water as separate measurable boundaries. Do not call the loop infinite until returned Water and every stored material remain stable over a long interval. Internal buffers can create temporary apparent gains.

Measure sustainable throughput

Treat Snowmaker as one boundary in a longer chain. Start with empty or recorded buffers, count how much four Water pixels and available Energy reaches the input during a fixed interval, and compare that with four Snow pixels leaving the output. Record material still inside the chamber. A growing reserve before the machine identifies an intake or processing limit; a growing reserve after it identifies a collection or destination limit.

Do not infer an exact rate from a short animation. Let startup material clear, repeat the interval, and test again after saving and loading. If supply arrives in bursts, record both average flow and the largest burst. Add parallel capacity only after the same boundary limits two clean observations. Otherwise extra machines can hide a routing fault while consuming space, power, heat, cold, or scarce construction resources.

Diagnose the first failed boundary

If Water rests above the machine without output, count whether four pixels are present and confirm Energy reaches the Snowmaker. If power is available but batches remain incomplete, inspect the fluid route for intermittent delivery or another destination drawing from the same Pipe network.

If Snow appears and then stops, clear the output and check the next thermal step. If the Water reserve falls faster than Snow arrives, measure the boundary directly around the machine to separate conversion from loss elsewhere in the network.

Apply the v0.5.6 version notes

The v0.5.6 announcement does not change the official four-Water, four-Snow, one-Energy operation. It does make Lasers melt Ice, which can affect nearby cold-material storage and release Water. Keep Laser work away from a Snow or Ice buffer unless the melt is part of the route.

Voltblub output is boosted in v0.5.6, but the announcement gives no exact rate. Do not assume one creature can sustain a chosen number of Snowmakers. Measure the connected battery during ordinary and temporarily petted states before sizing the power source.

Validate the design in a small test cell

Build one isolated Snowmaker with a limited input sample, visible output pocket, and a way to stop supply. Label the game version and active mods. Observe the expected transformation, any byproduct, where each pixel settles, and what happens when the destination fills. Then clear the cell and reverse the loading order if two materials share space. A repeatable small test gives a stronger design basis than a screenshot of a large factory.

After the test passes, copy the geometry into production while keeping access to the input, output, and removal controls. Leave enough room to inspect or drain the machine without opening a neighboring line. Recheck the route after patches that mention the machine, its materials, density, heat, fluids, energy, or building events. Keep the prior measurement with its version so a future change is visible instead of becoming an unexplained slowdown.

Use the pre-launch checklist

Before opening full supply, confirm that the input really is four Water pixels and available Energy, the planned result is four Snow pixels, every required power or temperature connection is active, and no incompatible material can enter. Verify output clearance, overflow capacity, a shutoff point, and a safe path for the player. Take one recovery save before connecting a rare or destructive input.

During the first long run, compare starting and ending inventory at every boundary. Watch for material trapped inside building cells, a mixed network, a full destination, and a reserve that only delays failure. If the line remains balanced through its normal burst and restart conditions, record the observed rate and promote the module as the factory's current versioned standard.

Field facts

Troubleshooting

• Water is present but no Snow appears.

  Confirm a complete four-pixel Water batch at the top and an active Energy connection.

• The machine works once and stops.

  Clear the Snow destination and verify that the next four Water pixels can reach the input.

• A circulation loop seems to create Water.

  Record every buffer and measure returned Water after startup effects; apparent gain can come from stored Steam or internal material.