No-Belt Linking and Connector Layouts

The first time Outworld Station's no-belt system goes wrong, it looks rude on purpose. Your machines are close. The icons look connected. The factory hums like it has a plan. Then one processor sits empty while the next machine starves two steps away, as if the whole station forgot what a box is. This is the moment to stop thinking in belts. Outworld Station uses linked modules and storage-style logistics instead of a visible conveyor lane. Your job is to make each link easy to read: what sends the item, what receives it, and what is allowed to store or pass it on.

A link is the logistics connection between modules. A connector, pipe connector, or linked storage node is best treated as a traffic point in that route, not as a magic splitter. Good layouts use short links, clear storage roles, and visible buffers. A buffer is a small storage stop that makes a shortage easy to see before the whole station starts doing silent office work in space.

The Basic Mental Model

Build every production chain as a short sentence: source, first machine, next machine, storage or demand. If you cannot say that sentence while looking at the layout, the station probably cannot read it cleanly either. 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 send rate 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 power work.
Linked storage or connector point	Helps organize requests, outputs, pipes, 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 fast.

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 second step beside that, and storage or the active demand point on the right. Add linked storage or a connector point only when the direct setup gets hard to read, the distance adds delay, or several machines need a clear shared feed. This makes a screenshot easy to read: inputs on one side, finished goods on the other, and no mystery spaghetti pretending to be science.

Place the source and first processor close enough that the link preview or link mode shows a valid connection.
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, or the next recipe step.
Watch the chain run for a short cycle before adding more machines.

Tip: when a chain stalls, rebuild the smallest broken section instead of tearing down the whole line. 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. It is faster than arguing with a silent logistics knot, and the knot has union backing.

Connector Rules That Prevent Most Stalls

Do not add link nodes just because there is empty space. Each one should solve range, routing, buffering, filtering, or visibility.
Keep one main direction per chain. Mixed backtracking makes it hard 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 that cannot stay powered is just modern art with a work order.

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 away, 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 send 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 when Outworld Station grows from asteroid handwork into real interplanetary industry.

The best early connector layout is not the prettiest one. It is the one you can debug while a power dip, a shipyard request, and a missing gas feed all take turns yelling at you. 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. This turns a messy station back into a set of clean supply chains, which is the whole point of the game: chaos in, industry out.

← Prev Next →