Sandustry Guide and Wiki

systems

Sandustry Blueprint Import and Export Safety Guide

Blueprint sharing can save construction time while hiding assumptions about version, startup state, surrounding geometry, and resources. A safe import workflow preserves attribution and tests the smallest risky boundary before the design touches valuable storage.

Early Access · sharing workflow · Checked 2026-08-22

Record source and version

Save the creator name, original link, posted date, stated game build, and any dependency notes. Do not remove attribution or rehost images and files without permission. If the build is unknown, label compatibility unverified. A blueprint's existence proves only that someone shared it, not that every current mechanic remains identical.

Back up before import

Exit or pause as required by current official guidance and create a dated backup of relevant save data before testing unfamiliar content. Verify the backup exists. Cloud synchronization is not a substitute for a local version because an unwanted imported state may synchronize. Use official support information for current paths and restore procedure.

Inspect the footprint

Choose clear space away from the main reservoir, valuable storage, hazards, and critical access routes. Check width, height, excavation, and surrounding fluid or material. An imported wall can redirect existing pixels even before the machines run. Preserve an escape and maintenance corridor around the full footprint.

Map every interface

Identify inputs, outputs, byproducts, power or controls, startup sequence, normal buffer lines, and overflow. If an interface is hidden or undocumented, do not connect it. Add temporary visible destinations and a limited source. A blueprint without a safe off state is an experiment, not a production module.

Run clean material tests

Feed one verified material at a low rate and watch the complete route. Keep outputs in quarantine. Then test a rejection or failure state when relevant. Do not begin with mixed valuable inventory. If the module behaves differently from its description, preserve the state and compare build context before modifying everything.

Test failure and reload

Fill an output, stop an input, stop controls, save, reload, and restart as separate tests. Observe whether stored pixels settle, fluid levels change, or a launcher misses its catch zone. A design that requires manual clearing needs explicit access and recovery notes before production use.

Adapt without erasing provenance

Document every geometry or component change and why it was necessary. Keep the original blueprint reference. Do not republish the modified file as entirely your own. Separate current-build observations from creator claims, and avoid promising compatibility beyond the version you actually tested.

Export a useful package

When sharing your own blueprint, include build, purpose, required unlocks, inputs, outputs, startup, shutdown, full-output behavior, known limits, and test evidence. Use original diagrams or permitted screenshots. Invite users to verify rates locally rather than advertising an unsupported universal optimum.

Use an import acceptance sheet

Before production connection, score the imported module against a written acceptance sheet: source and creator recorded, build context known, footprint clear, required unlocks available, every interface labeled, limited input installed, outputs quarantined, overflow contained, manual stop accessible, and reload tested. Mark each result pass, fail, or unknown. Unknown is not a failure, but it prevents the module from being described as verified. After adapting geometry, rerun the sheet and preserve a note explaining the change. When exporting, include the completed sheet so another player can distinguish your observed behavior from assumptions. This documentation also protects the creator: compatibility problems can be discussed as specific build or interface differences instead of vague claims that the blueprint is broken. Keep the test save until a second normal run succeeds, and disconnect the module immediately if an unknown output escapes quarantine.

Sources and evidence notes

Frequently Asked Questions