Self-Locking Package Storage (18 Vaults)

A Create 6 package storage that never sends a package unless it’s guaranteed somewhere to land.

One buffer feeds 18 max-size vaults (two mirrored sides of 9). Threshold switches on every vault keep track of how much room is left, and the system sends at fast, medium or slow speed depending on how full the vaults are. When everything is full it locks itself, and the buffer keeps holding new items, still requestable through its stock link. Take items out and it unlocks and refills by itself. No packages stuck on belts, nothing lost, and it works at any RPM thanks to belt-loop clocks.

After placing it:

1. Set all 54 threshold switches (signs on the back mark columns A, B, C): count in stacks, empty filter, Invert on.
   A: top 1,432 / bottom 1,431 · C: 1,567 / 1,566 · B: 1,612 / 1,611
   Only if you always run at 256 RPM you can set:
   A: top 1,558 / bottom 1,557 · C: 1,585 / 1,584 · B: 1,612 / 1,611

2. Drop one item on the belt clock at the top.

3. The 6 input frogports at the front: send and receive, all with the same name (e.g. Storage). Every other frogport: no name, send only.

4. Connect rotation, 256 RPM recommended (avoid 72–80 RPM).

Lights: the 4 at the top flash with each packager so you can see the speed, and the light at the front means storage is full.

Limitations and safeguards

Because this system operates entirely through packages, it cannot make use of leftover space that is insufficient for a complete package. Each package contains 9 stacks, meaning that the final 9 stacks of available space in a vault may not always be filled completely. In some cases, this can leave a small amount of unused capacity that the system will not automatically fill, simply because the remaining space cannot accommodate another full package. However, given the sheer storage capacity of the 18 max-size vaults, this is a negligible trade-off in practice.

The loopback path that returns packages to the buffer serves as an additional failsafe rather than a normal part of the system's operation. During testing, with the threshold switches configured correctly, the system did not send packages that could not fit into the main vaults, making the loopback rarely, if ever, necessary. It is retained as a safeguard against packages reaching the distribution system when the intended storage cannot accommodate them.

Full documentation, how it works, test results and settings for every speed: github.com/DumiFlex