No-Belt Linking and Connector Layouts

The first time Outworld Station's no-belt system fails, it can look like the game is being rude on purpose. The machines are close. The icons look connected. The station is humming. Then one processor sits empty while another machine starves two steps away. That is your sign to stop thinking in belts.

Outworld Station is built around linked modules, inventory pairing, storage, and connector routes instead of visible conveyor lanes. Your job is to make each chain easy to read: what sends the item, what receives it, and what is allowed to store or pass it along.

A link is the logistics connection between modules. A connector, pipe route, or linked storage module should be treated as a planned traffic point, not a magic splitter. Good base layout starts with short links, clear storage roles, and visible buffers. The developer has said connectors are not the main item-throughput limit; each building has its own maximum automatic output rate, so too many buildings feeding one output can still create bottlenecks.

The Basic Mental Model

Build every production chain like a short sentence: source, first machine, next machine, storage or demand. If you cannot say that sentence while looking at the layout, the chain will be hard to debug.

This is the big shift from Factorio-style belts. You are not watching items move along a lane. You are checking whether each module has a valid sender, receiver, output path, filter, and enough building output capacity to keep up.

Layout Part	What It Does	Good Early Habit
Source	Feeds raw material into the chain.	Keep it close to the first processor when possible.
Processor	Turns input into a more useful part.	Leave one open side for later links or support work.
Linked storage or connector point	Helps organize requests, outputs, pipe routes, or short transfer routes.	Use it as a planned node, not a random patch.
Storage or demand	Catches output or feeds an objective.	Place it where you can see shortages quickly.

A Clean Starter Layout

For your first stable no-belt layout, use a simple left-to-right block. Put the resource source on the left, the first processor beside it, the next step beside that, and storage or the active demand point on the right. This makes the whole chain easy to scan: inputs on one side, work in the middle, finished goods on the other.

Add linked storage or a connector point only when the direct setup becomes hard to read, distance creates delay, or several machines need a clear shared feed. Extra nodes should make the layout cleaner, not turn it into hidden spaghetti.

Place the source and first processor close together, then create the intended link or inventory pair.
Add the next machine only after the first machine is receiving input and making output.
Use a small storage buffer between stages if distance, filters, or layout space makes the direct handoff hard to debug.
Route finished goods to storage, shipyard demand, research, or the next recipe step.
Watch the chain run for a short cycle before adding more machines.

Blueprint-Style Starter Base Layout

Outworld Station 1.0 added one-off blueprints through duplicated building groups, but this example is only a planning pattern. Do not treat it as a saved or shareable blueprint. The best early layout is usually a compact rectangle with one input edge, one working middle, and one output edge.

The goal is not to make the prettiest station. The goal is to make a starter base layout that shows you what broke without opening every panel.

Block Position	Place Here	Why It Helps
Left edge	Raw source, intake, or nearby storage for the material you are feeding.	Keeps the start of the chain obvious.
Center-left	First processor or refinery step.	Shortens the most important early link.
Center-right	Second processor, crafter, or follow-up recipe step.	Makes upgrades easier without crossing the whole station.
Right edge	Output storage, shipyard feed, research feed, or the next district input.	Shows whether the chain is producing or backing up.
Top or bottom lane	Power, gas, pipes, or service routes.	Leaves room to fix support bottlenecks without moving the whole block.

If you want a second safe pattern, use a small hub-and-spoke layout for shared inputs. Put one visible storage or connector point in the middle, then link only a few nearby machines to it. This works when several recipes need the same material, but it gets messy if every machine on the station uses the same hub. Once a hub feeds too many jobs, split it into smaller local blocks.

Best Early Layout Checkpoints

Inputs enter from one side instead of three directions.
Finished goods leave from one side or one clearly marked storage point.
Each connector point has a reason: distance, routing, buffering, filtering, pipes, or visibility.
Support systems have service space before the block is packed tight.
The layout still makes sense after you add one more machine to the chain.

Tip: when a chain stalls, rebuild the smallest broken section first. Remove the last added link, storage node, or machine. Confirm the older part works again, then add the new part back with a cleaner route. This is faster than tearing down a whole line.

Connector Rules That Prevent Most Stalls

Do not add link nodes just because there is empty space. Each one should solve distance, routing, buffering, filtering, pipes, or visibility.
Keep one main direction per chain. Backtracking makes it harder to see which machine is feeding which target.
Separate raw inputs from finished outputs when space allows. Shared storage clusters are where shortages hide.
Put high-demand chains near their demand point before you optimize low-use parts.
Leave service space around power, gas, and pipe needs. A perfect item layout is not useful if it cannot stay powered.

Common No-Belt Failures

Symptom	Likely Cause	Fix
Machine has power but no input.	The source is not linked, is filtered wrong, is too far from a useful buffer, or is feeding another request first.	Check the direct link, filter, and local storage request before adding more machines.
One machine runs, the next stays empty.	Output is not reaching the next recipe step, or the sender's output rate is the bottleneck.	Move the machines closer, add a small buffer, or route output into visible storage first.
Storage fills while an objective starves.	The chain ends at storage but does not continue to the demand point.	Add a clear link from storage or output to the active demand.
Everything is linked, but production is slow.	Power, gas, pipe flow, or module output rate is throttling the chain.	Check support systems and output rates before adding more machines.
Adding a new branch breaks the old one.	One shared storage or link cluster is serving too many jobs.	Split the branch into its own local path and give it a clear output.

Use Layout Blocks Like Districts

Once the starter chain works, group your station into small districts. A district is a local block that handles one job: raw processing, part crafting, shipyard feeding, fuel or gas support, or export prep. Each district should have a clear input side and a clear output side.

This keeps the linked logistics system readable as Outworld Station grows into larger station networks. Before you expand, point at each district and answer three questions: what feeds it, what does it make, and where does the output go? If any answer is vague, fix that link before building outward.

Before You Expand

Confirm each active machine has input, output, and support systems.
Put a small storage buffer at the end of important chains so stalls are visible.
Keep link branches short until you understand their demand.
Do not copy a belt-game bus unless the links are actually doing useful work.
Stabilize shipyard or research feeds before starting a new station-scale project.

If you are stuck, pick one product that matters right now and trace only that product. Start at the demand point, then walk backward through storage, link, machine, and source. The first empty, filtered, full-output, or unlinked step is the real problem. Fix that, let the chain run, then move to the next product. That turns a messy station back into a set of clean supply chains, which is the real point: chaos in, industry out.

← Prev Next →