Gateway Routing
A Gateway Core can bind up to 16 destinations (“channels”). Normally a Gateway Port or Storage Bridge only talks to the active channel. Turn on route mode and each item fans out to whichever channel’s filter accepts it — one Core can sort iron to one base, gold to another, and everything else to a third.
Enabling route mode
Section titled “Enabling route mode”- Right-click the Core to open the destination picker.
- Toggle Route: ON/OFF (hidden if the server sets
gateway.allowFanOut = false). - Route mode is a property of the Core and applies to every Port and Bridge on that ring.
Defaults off with empty filters, so existing 1.0 worlds behave unchanged until you opt in.
Per-channel filters
Section titled “Per-channel filters”In the picker, right-click a channel to open its filter editor: nine ghost slots plus a Whitelist / Blacklist toggle. Click a slot with an item to add a filter copy (nothing is consumed); empty-handed click clears a slot.
| Mode | Empty filter means |
|---|---|
| Whitelist | Accepts nothing — an unconfigured channel receives nothing |
| Blacklist | Accepts everything — useful as a catch-all |
How an item picks a channel
Section titled “How an item picks a channel”For each item, the Core walks channels in order (1 → 16) and sends it to the first bound channel whose filter accepts it. Routing is deterministic — a given item type always lands on the same channel, so items never bounce between destinations. An item that no channel accepts is not moved (it stays in the Port’s send buffer or the local storage network).
Ports and Bridges
Section titled “Ports and Bridges”Gateway Port. Items funneled into the Port are sorted to the matching channel’s partner ring. Fluids are not item-filterable, so they always follow the active channel. With route off, the Port behaves exactly as in 1.0.
Storage Bridge. Passive push pulls from the local network only items some channel accepts, and delivers each to that channel’s partner network. In route mode the channel filters are the only gate — the Bridge’s own push filter is ignored. Passive pull and the terminal Partner tab still use the active channel; fan-out is a send concern only.
What the active channel still owns
Section titled “What the active channel still owns”Unchanged by route mode:
- Player travel
- Fluid transfer
- Manual / terminal item moves
- Bridge pull
Route mode only changes where pushed / sent items go.
Fuel and safety
Section titled “Fuel and safety”Routed transfers pay the same per-flush fuel as normal and are gated by a Gateway Flux Battery reserve the same way. A channel whose partner chunk is unloaded holds its share (buffered, retried) while other channels keep flowing — no dupe, no loss.