Sandustry Guide and Wiki

systems

Sandustry Puzzle and Progression Troubleshooting

A puzzle can become harder to diagnose after terrain, fluid, or objects are moved. This workflow preserves evidence and separates navigation, interaction, resource, and possible bug states before escalating to a spoiler or destructive workaround.

Early Access · spoiler-light method · Checked 2026-08-22

Capture the untouched state

Before more digging or moving material, record the room, entrances, symbols, nearby structures, inventory, and build. Note what changed since arrival. Use a local screenshot only for personal diagnosis unless sharing is permitted. Preserving the initial arrangement makes official or community help more likely to match your situation.

Define the blocked outcome

State whether you cannot enter, activate, route material, survive a hazard, collect a result, or trigger progression. Avoid saying only ‘the puzzle is broken.’ A precise outcome separates missing access from an interaction sequence, insufficient resource, wrong tool, or a state changed by earlier excavation.

Read local evidence first

Inspect visible symbols, material paths, machinery, vertical space, and nearby discoveries. Sandustry combines terrain and physical materials, so geometry may be part of the clue. Do not assume every object is decoration or every obstruction should be destroyed. Compare current official terminology when identifying a building or resource.

List controllable variables

Write the actions you can reverse: move a small sample, toggle a control, change one route, return an object, or approach from another side. Separate them from destructive excavation and resource consumption. Test reversible actions first and keep the rest of the room unchanged so each result has meaning.

Test one hypothesis

Predict what should change, perform one action, and observe all outputs. If nothing changes, restore the state when possible before testing the next idea. Repeated random actions can create a new configuration not covered by any guide. Save before a destructive or irreversible attempt using current official save guidance.

Check progression prerequisites

Confirm whether the current objective, tool, research, artifact, or access route is actually available. Do not invent a prerequisite from an old walkthrough. Use the official FAQ and Wiki for documented systems, then compare your build and objective state. A puzzle may be reachable before it is intended to be completed.

Separate bug from incomplete understanding

Restart or reload only after recording the state. Compare a clean approach or another save when practical. If the same minimal steps fail with the documented prerequisite, collect build, platform, location context, expected result, actual result, and reproduction frequency for official support. Avoid destructive save edits or unknown downloads.

Ask for targeted help

Share the exact blocked outcome, build, relevant objective, what the room looked like initially, and reversible tests already performed. Request the smallest hint first if avoiding spoilers. Treat old demo solutions and community answers as candidates until they match current evidence. When solved, record which observation mattered instead of copying an unexplained sequence.

Build a spoiler-safe evidence packet

If local testing does not resolve the block, prepare a concise packet before asking for help: build and platform, current objective, location description, untouched-state image or sketch, relevant inventory or unlocks, exact blocked outcome, reversible actions tried, and whether reload reproduced it. State how much spoiler detail you want. This lets another player answer the missing observation rather than posting an entire sequence from a possibly different version. When a solution works, add the prerequisite and decisive clue to your notes, not copied dialogue or screenshots. If the same documented state still fails, reuse the packet for official bug reporting and remove personal information from logs or saves.

Sources and evidence notes

Frequently Asked Questions