Blueprint Protocol
Copy factory modules without copying their mistakes. Audit inputs, states, throughput, safety shutoffs and overflow before deployment.
How Blueprint Protocol works
Deploy this when
You can isolate the module, observe a full cycle and provide a deliberate overflow route before connecting the main supply.
Delay this when
The required material states, filters or safety shutoffs are still missing. A copied layout cannot replace its operating conditions.
Pre-flight inspection
A blueprint can be perfectly valid and still fail in your base. Terrain, available height, unlocked filters and material supply all change the operating envelope.
Before pasting, record six facts:
- The exact input materials and their states.
- The expected output and any secondary byproducts.
- The tallest gas or launcher path in the module.
- Which filters are allow-list and which are block-list.
- Where excess input exits when the machine is full.
- What stops heat, water or electricity during a jam.
Module boundaries
Good blueprints expose connection points. Inputs arrive on one edge, outputs leave on another, and the machine can be tiled without overlapping hidden storage.
Leave a one- or two-tile inspection corridor around the first copy. Once the module survives real throughput, close the gap or repeat it. Debugging a dense megafactory is slower than validating a single cell.
Start-up sequence
- Place the empty structure.
- Confirm every belt, filter and launcher direction.
- Prime heat, water or electrical buffers.
- Add one small input batch.
- Watch the first output and every byproduct reach its destination.
- Test the full-buffer state before connecting the main bus.
Failure modes
- A copied filter keeps its visual tile but not the intent you assumed.
- A tileable design still requires space for launch spread or gas rise.
- Throughput claims often assume uninterrupted, clean input.
- A machine without overflow behaves correctly only until its first full buffer.