Blueprints

A blueprint is a saved snapshot of a region's entities with relative positions, rotations, and configuration (recipes, filters, circuit settings, sometimes tiles). State owned: a library of blueprints plus placed ghosts awaiting construction. Capture copies selected entities into a blueprint; stamping projects its entities at a cursor with rotation or mirroring, checks placement validity, and creates ghost build orders that construction agents or the player fulfill. Export serializes a blueprint to a string or file that other players can import. Canonical form: Factorio blueprints, blueprint books, a personal library that persists across saves and is visible to other players in multiplayer, and exchange strings used by community sites. Others: Dyson Sphere Program and Satisfactory blueprints, Mindustry schematics shared as text, and Space Engineers ship blueprints rebuilt through projectors.

Solving a layout once is enough. The player designs a module carefully, then scales it by stamping, which moves attention from placing pieces to designing systems. Imported community designs let newcomers skip solved problems; some players feel that copying removes the puzzle.

• unlock timing: available from the start or gated behind progression such as construction robots
• what is captured: entities only or also configuration, tiles, and logic
• parameterized blueprints that substitute items or values at placement
• sharing scope: within a save, across saves, or exported strings and workshop integration
• who fulfills placed ghosts: the player by hand or automated builders
• validity rules when stamping over obstacles or partial resources

• Imported meta designs replace the core puzzle, and players report feeling they are executing other people's solutions.
• Late unlock makes the repetitive early game tedious and drives players to mods.
• Blueprints that break when stamped into slightly different terrain or orientation cost more time than rebuilding by hand.

• Modular, tileable designs become dominant because they stamp cleanly, shaping the visual language of player bases.
• Shared blueprint strings create a design culture of named, versioned community layouts.
• Stamping lowers the marginal cost of expansion, so growth becomes limited by resources and logistics rather than player time.

• Can generative models produce valid blueprints from a goal such as a 45 per second green circuit block, and does that remove or relocate the design puzzle?
• How should parameterized blueprints be represented so designs adapt to terrain and recipes without becoming full programming?