VOCABULARY
Blueprint, design, layout, string
Player language overlaps, but the objects are not identical.
Construction copy / paste
A current in-game shortcut for reproducing a selected build without rebuilding every component manually.
Blueprint string
A shareable encoded representation used by current community products and players. Compatibility must be checked in the current build.
Factory design / layout
The arrangement and logic: purpose, footprint, inputs, outputs, material states, and known constraints—even when no string is attached.
SAFE WORKFLOW
Copy the system, not just the footprint
The exact buttons can change during Early Access; the verification logic should not.
- 01SELECTChoose a working area
Start from a layout that visibly completes its task.
- 02COPYUse current copy tools
Reproduce locally before sharing outside the save.
- 03CONTEXTRecord version + I/O
Name inputs, outputs, footprint, and purpose.
- 04TRANSFERShare through a verified method
A string is data, not proof that the design works.
- 05TESTVerify after import
Check orientation, connections, resources, and output.
FIRST-PARTY VISUAL ANCHOR
Context is part of the design.
The first-party capture shows why a layout record needs more than a footprint: terrain, liquid boundaries, and long material routes are all visible. It is not a blueprint record or download.
WORKFLOW, NOT A TOOL UI This sequence deliberately avoids inventing button labels or an import interface that has not been independently verified for this site.
COMPATIBILITY
Five checks before you trust a shared layout
- 01Game version
Was the design built and retested on your current Early Access branch?
- 02Purpose
What exact problem does it solve—water capture, heat, sorting, or another task?
- 03Inputs / outputs
Which materials and states enter, and what stable result should leave?
- 04Environment
Does it depend on terrain, gravity, a biome, an external source, or a specific orientation?
- 05Visible test
Can you see the complete process run, including recovery from the common failure?
LAYOUT RECORD
What a trustworthy design description includes
This is a documentation pattern, not a fake blueprint card.
- NAME
- Plain-language task
- VERSION
- Last build tested
- PURPOSE
- One measurable output
- FOOTPRINT
- Width × height + orientation
- INPUTS
- Material + required state
- OUTPUTS
- Material + expected rate/state
- CONSTRAINTS
- Terrain, heat, fluid, research
- PROOF
- Current visible test + creator
Good description
“Current EA water-capture concept. Input: Cryoblaster snow. Output: contained rainwater. Requires open sky and a reservoir. Retest after fluid or weather patches.”
Weak description
“Best infinite water blueprint.” It gives no version, dependencies, proof, or recovery path—and makes an unverified superiority claim.
EXTERNAL RESOURCES
Community products are discovery sources
Their existence does not turn this page into a competing library.
SandustryVault / SandPrints
A current community blueprint product can help reveal the language and metadata players expect. Records still need creator, version, and in-game verification before you treat them as evidence.
PRODUCT BOUNDARY
What you will not find here
A future library would require a real dataset, creator rights, version testing, moderation, and separate product approval. Until then, this page remains a complete guide and honest hub.
EVIDENCE LEDGER