Sandustry Thermal Buffer Guide: Heat, Cold, Lava and Cinder

Understand the machine's job before placing it

The Thermal Buffer turns temperature into a manageable factory resource. It can collect heat or cold and support processes that need a stable thermal condition. Its useful capacity is therefore not only physical space: the direction and amount of stored temperature determine what the next input will do.

Treat a hot buffer and a cold buffer as different operating states. Label the intended state and isolate incompatible sources. A buffer crossing through zero may stop producing the expected result even while materials continue to arrive, so temperature should be observed alongside material flow.

Follow the documented input and output rules

The official page documents interactions with Fire, Lava, and Snow. Update #3 adds the current Lava rule: when the Thermal Buffer is cold, meaning its temperature is negative, Lava adds less heat and turns back into Cinder instead of being fully consumed. The returned solid needs somewhere to leave.

The phrase less heat is comparative, not an exact rate. Do not publish or design around a guessed number. Measure the starting temperature, the amount of Lava introduced, the ending temperature, and the Cinder returned in a controlled v0.5.6 cell. Repeat only after restoring the same starting condition.

Build a serviceable layout

Give Lava a limited input pocket and Cinder a separate gravity or conveyor exit. Keep the temperature source serviceable so Snow, Fire, or another documented input can be stopped without opening the Lava path. Provide containment that v0.5.6 Lava does not destroy.

Install an upstream shutoff and leave free space around the output. If Cinder accumulates against the buffer, the material cycle can stall even though temperature remains available. Keep artifact-room experiments separate because Update #3 fixed a case in which a Thermal Buffer consumed Lava while surrounding terrain self-healed.

Diagnose the first failed boundary

If Lava disappears without returned Cinder, verify that the buffer was still below zero at the moment of contact. If Cinder appears but the process slows, inspect output clearance and whether repeated Lava input has warmed the buffer toward zero. Recreate the starting temperature before comparing batches.

If behavior changes only inside an artifact room, confirm v0.5.6 and reproduce it in an ordinary test cell. This distinguishes the special self-healing environment from the general machine rule. Preserve the affected save before digging or exposing more Lava.

Apply the v0.5.6 version notes

The negative-buffer Lava return is new in v0.5.6 and supersedes older explanations that treat Lava as fully consumed in every Thermal Buffer state. The same patch raises Lava density to 200 and lets it destroy Fluxite, Redsoil, and Strataform, so both input routing and containment need review.

Update #3 also fixes the artifact-room self-heal interaction. Remove old workarounds one at a time, test a small batch, and reload the save before declaring the route repaired. A current-version recovery copy should remain available until the line completes a normal long run.

Field facts

Troubleshooting

• Returned Cinder blocks the input.

  Stop Lava, clear the dedicated Cinder route, and reopen a limited feed only while the buffer remains negative.

• The same Lava batch adds a different result.

  Compare starting temperature and game version; restore the same negative state before measuring again.

• Artifact-room behavior differs from a test cell.

  Confirm v0.5.6, preserve the save, and isolate the room-specific self-healing interaction from the normal buffer rule.