Skip to content

Codex Storage Overview

CaptainGummiball edited this page Nov 10, 2026 · 1 revision

The Storage Network

A storage network keeps items, fluids and gases in one place and lets you reach all of it from one screen. It has no cables: every block is tied to a Storage Controller with the Quanta Linker.

The parts

How it works

  1. Place a Storage Controller and the members you want.
  2. Link each block to the controller: use the linker on the block, then on the controller (see Linking).
  3. The members join the network as soon as both they and the controller are loaded. From now on the network sees the contents of all of them as one.
  4. Open a terminal to take and store by hand; use a Storage Interface for pipes.

Where things go

When something is stored, the network fills its own members first: first those that already hold this kind, then the others. Only what is left goes into foreign storages behind External Storage Interfaces, again first into those that already hold it. When something is taken out, own members give first, foreign storages after them.

Every kind counts on its own: an enchanted or damaged item is another kind than a plain one, and each fluid and gas is a kind of its own.

Contents stay in the blocks

The contents belong to the member blocks, not to the controller. A unit keeps its items while its chunk is unloaded, and a broken unit keeps them in the dropped block. The network itself only remembers its reservations (amounts that the Factory Controller holds back for a job).

Nothing is ever loaded by the network. A member whose chunk is not loaded is simply not part of the network until it loads again; its contents are then missing from the terminal for that time.

Note

Link range Every member must be within 96 blocks of its controller and in the same dimension. If the server lowers general.linkRange (default 96, allowed 16–512) later, members that are now too far stay linked but go offline.

Teams and rights

Whoever places a storage block owns it. The owner's team decides what others may do, see Teams and Rights:

Right Allows
Viewer Open terminals and interfaces and look at the contents.
Operator Take and store items through a terminal.
Admin Link and unlink blocks, change filters and modes.

A terminal needs the right on the terminal and on its controller. Without it the action bar says "No access: this needs a higher role in the owner's team."

Note

Bulk Tank and Warehouse belong to their network The controllers of the Bulk Tank and the Warehouse have no owner of their own: once linked, only who may manage your Storage Controller (you and the admins of your team) can unlink them or link them elsewhere. An unlinked one can be linked by anybody, so link it right after building it.

Switching the module off

The server can switch off all storage blocks with features.storage (default true). Switched-off blocks do nothing, offer nothing to pipes and cannot be crafted; a terminal still hands out what you take, but takes nothing in.

Typical mistakes

  • The terminal says "Not linked": link the terminal itself to the controller, not only the units.
  • Items missing: a unit is unloaded, out of range or was broken. Right-click the unit: the last word of its line says "online", "linked, offline" or "not linked".
  • The network is full although a unit has room: a unit is also full when it holds as many kinds as it may. Look at the kinds bar of the terminal.
  • The controller was broken: the network ends and every loaded member forgets its link. Place a controller and link the members again.

QNet Codex

Getting Started

Energy

Processing

Rift

Storage

Logic

Reference

Items and Blocks

Clone this wiki locally