Sandustry Blueprints: What the Sources Actually Confirm
The sources confirm that factory sections can be selected, copied, and pasted, while community builders share blueprint strings through Sandustry Vault and Discord. They do not document every import-screen step, so this page avoids inventing one.
What the collected sources confirm
The official beginner material documents selecting structures with C and using Ctrl+C and Ctrl+V to copy and paste. Community build sources also mention blueprint strings shared through Sandustry Vault and the official Discord’s build-sharing channel. These are the supported facts behind the Sandustry blueprints keyword.
The keyword-specific research file mostly contains Artifact-puzzle material rather than a complete blueprint interface reference. It does not verify every button, file location, or import prompt. This guide therefore describes a safe use pattern without fabricating missing UI steps.
Copy a working factory section
Select a section only after it has processed several batches without clogging. Include the structures that control input and output, not just the central machine, because a Shaker or Press depends on the surrounding collection and filtering. Paste the section into an area with equivalent clearance and containment.
Falling solids and flowing liquids react to the destination terrain. A copied Launcher path can hit a wall, and a copied liquid chamber can leak through a corner that was sealed in the original location. Treat the pasted result as a new installation that still needs observation.
Use community blueprint sharing carefully
The collected build discussion points to Sandustry Vault as a place where players share in-game blueprint strings. It also references the official Discord channel used for sharing builds and unusual compact arrangements. Those sources establish that community exchange exists, but they do not guarantee that every shared layout matches the current game version.
Read the creator’s stated purpose before importing or rebuilding a design. A showcase may optimize compactness, visual effect, or a specific patch rather than reliable throughput. Custom-map builds can also depend on resources or rules that are not available in a normal generated world.
Validate each imported design
First identify the intended input material and the expected outputs. Then confirm the required research, tool, building orientation, and open space around the module. Feed a small batch and watch every item, liquid, or gas reach the next stage before connecting continuous production.
Check all filters because a single reversed allow-or-block choice can divert the main resource. Confirm that outputs do not stack above processing surfaces and that recycling loops do not grow without a release path. For liquid builds, keep each fluid network isolated and inspect every corner.
Respect the limits of the evidence
No collected source provides a complete current-version blueprint import manual. It would be misleading to invent a menu name, storage directory, or keyboard shortcut beyond the documented copy and paste controls. If the live interface differs from a community post, follow the current in-game labels.
Blueprints also do not replace progression. A copied late-game module still needs the relevant research, inputs, tools, and space. Use shared builds as tested arrangements to study, then verify every dependency in the world where they will run.
Source notes
This guide consolidates only the collected official, developer, Steam Community, video transcript, and community material available for this keyword. Version-specific or community-observed behavior is identified in the text; unsupported details are omitted.