Repository navigation
FAQ
Check, in this order:
- Do both ends share a channel and a route? Same channel, identical route name. This is almost always the answer.
- Are both endpoints enabled? A disabled endpoint neither accepts nor sends.
- Is there anything to send? The input needs a supplying belt or pipe with cargo on it.
- Can the output deliver? If its buffer is full, the receiving belt cannot keep up. That is a factory problem, not a route problem.
- Fluid route type. A fluid route carries one fluid at a time; sending a second type does nothing until the route is emptied.
They are colour-coded and carry different glyphs: mint for input, orange for output. The build menu clamps a tile label to two lines, which is also why the names are short.
No. An output receives whatever the inputs on its route send. If you need separation, use separate routes. Items keep their order and state through a route, so a single mixed route into a sorting area works well.
No. The buffers are 64 items or 50 m³ and exist to smooth belt timing. Nothing is stored between sessions beyond what happens to be buffered.
Yes, but the route must be empty. Every endpoint on it must be disabled and drained, and connected pipes must be empty or already contain the new fluid. The endpoint window tells you which condition is not yet met.
No. Flush discards only the endpoint's local buffer. Your pipe network is untouched. It asks for confirmation, and needs the endpoint disabled first so nothing refills it mid-flush.
Take them first. Item endpoints let you move buffered items into your own inventory, so nothing is destroyed. Drain before reassigning, or the old route's cargo is delivered to the new one.
No. Item and fluid endpoints have no electrical connection, so a brownout cannot strand your supply lines. Only the hub (5 MW) and the Personnel Teleporters (50 MW each end) draw power.
No. The Default channel works with no hub anywhere. Build one when your network is large enough that searching a list beats walking to the building.
No. Losing hub power disables the management interface, not logistics. Routes keep carrying cargo.
No, pioneers only. Both ends need 50 MW at the moment of travel, and a journey reserves the destination for 30 seconds, so a busy destination will not accept a second traveller.
The way the placement arrow points. Aim it somewhere useful when you build.
No, and this is deliberate. SML writes settings per client, so a gameplay number in there would let one player's client disagree with the host. The settings are interface preferences only. See Multiplayer and dedicated servers.
Raise the window refresh interval under Mods in the pause menu. It controls how often an open window re-reads the network and affects nothing about transport.
- No item filtering, no priority between outputs, no shared storage.
- Fluid routes carry one fluid type at a time.
- 256 routes maximum.
- Linux dedicated servers and controller input are not currently certified.
- Pre-1.0: full retail multiplayer, progression and save-reload acceptance is still in progress. Keep save backups.
Open a GitHub issue with your Satisfactory build, SML version, whether you are on a dedicated server, what you expected, what happened, and FactoryGame.log if the game misbehaved.