Sandustry Guide and Wiki

troubleshooting

Sandustry Puzzle Reset: Recover a Stuck or Changed Room

Players use 'reset' for different failures: escaping the room, restoring controls, repairing a Lava-dependent artifact room, or fixing progression. This guide keeps those paths separate and uses only the narrow recovery behaviors documented in official v0.5.4 and v0.5.6 notes.

Early Access v0.5.6 · evidence boundary corrected 2026-09-05 · Checked 2026-09-05

Match your room: water, lava, ice or circuits →

Identify what is actually stuck

If the player cannot leave, use the escape path. If a reset button, door, red block, water source, or indicator is wrong, use the room-state path. If the room completed but the next factory tier remains locked, use the progression path. Do not reload repeatedly until you have written down which state failed.

Capture the version shown by Steam or the game, platform, room appearance, current objective, last successful action, and whether the failure survives leaving the area. This prevents three unrelated problems from being reported as the same 'puzzle reset' bug.

Handle a physically trapped character separately

The current Early Access sources checked here do not document a universal player-position recovery command. Record the room first, inspect the current pause menu and keybindings, and avoid digging through an unknown puzzle boundary.

If a current in-game recovery control is visible, use only its displayed scope and then inspect the room separately. If no such control exists, preserve the save and report the player-position problem through the official channel. Neither path should be described as regenerating materials, reopening doors, or repairing objectives.

Verify that update 0.5.4 or later is installed

Official Steam notes for v0.5.4 say reset buttons in puzzles can no longer be deleted. They also say a deleted reset button will be restored on reload. SteamDB records the corresponding August 16 build as 24767486, providing a second public record for the patch date and contents.

If Steam has not updated, exit the game and let the client finish the update before testing the room again. Do not assume a save created on an older build has already received every repair while the game is still running. Record the post-update build before drawing conclusions.

Recover a missing reset button

On v0.5.4+, make a normal save where possible, return to the menu, and reload once. The official patch note specifically says reload restores a reset button that had been deleted. After loading, inspect the control before moving water, blocks, or terrain. This gives the documented repair a clean test.

If the control is still missing, capture the room, build, save origin, and exact location before trying anything else. Do not manufacture a replacement or copy unknown save data. A persistent missing button on the patched build is reportable because it contradicts a narrowly documented recovery behavior.

Recover red blocks on a puzzle door

The same official notes say closing and opening the door should restore red blocks on puzzle doors. Test that exact sequence once while keeping the rest of the room unchanged. This instruction applies to puzzle doors; it should not be generalized to every red block in the open world.

The patch also allows small demolisher operations for certain red-block problems, limited in the note to scans of 256 tiles or fewer. Because demolition changes terrain, treat it as a later recovery step and only within the documented scope. Preserve a backup and avoid a broad selection.

Reload a Lava-dependent artifact room on v0.5.6

Update #3 says Thermal Buffers no longer consume Lava inside artifact rooms. If that earlier behavior soft-locked a puzzle, the official note says the room should self-heal on load. Confirm public build 25106127 or later, record the room, and perform one clean reload before moving external Lava or demolishing boundaries.

This repair applies to the documented Thermal Buffer and Lava failure state. It does not prove that every lunar, water, circuit, or door puzzle will regenerate its resources. If the specific room does not heal, preserve build, save age, before-and-after state, and the visible Thermal Buffer/Lava condition for an official report.

Treat water-loss reports as symptoms

A current Reddit report asks how to reset after water became caught in a puzzle. Replies propose pressing the button again and describe a gravity-routing solution. Those comments prove that the symptom exists for at least one player, but they do not establish an official regeneration rule for every room.

Try the room's visible reset control only after confirming the patched button state. Observe whether the source, indicators, and placed blocks change. If no documented control restores the attempt, report the exact result instead of promising that restart, reload, or repeated button presses always regenerate water.

Use a reversible recovery ladder

Use this order: capture state; verify build; separate player position from room state; test the visible reset control; reload once for a missing button or the v0.5.6 Thermal Buffer/Lava repair; close and reopen a puzzle door for documented red-block restoration; then stop. Each step has a defined target and keeps the next observation interpretable.

Avoid deleting large regions, flooding the room from outside, installing mods, or modifying saves during diagnosis. Those changes may make the room completable while destroying the evidence needed to determine whether the original state was a game bug.

File a useful bug report

Include platform, exact version, save age, room description, objective, steps from a clean load, expected result, actual result, and frequency. Attach your own screenshot and logs only through an official channel, after checking them for personal information. Mention whether the v0.5.4-specific reload or door sequence was tested.

A concise reproduction is more useful than a long list of random experiments. If the room worked after reload, report that too: intermittent state restoration can still help developers identify timing or persistence issues. Keep a backup before sending a save.

Sources and evidence notes

Frequently Asked Questions