Rail System Guide: Routing, Drone Paths, Upgrades & Jams

StarRupture Rail System Guide: Routing, Drone Paths, Upgrades & Jams

Trust boundary: official Update 1 material confirms building stability, Drone Smart Path, drone priority, and upgrades from slower Drone Rails without deconstruction. Community discussions help identify multi-feed, crossing, elevation, and jam scenarios, but they do not establish a universal throughput number or one optimal layout.

If you searched for a StarRupture rail guide, start with the routing problem you actually have: a disconnected machine, an unclear drone path, a crowded crossing, or an upgrade decision. This page owns that diagnosis. Use the Factory Layout Guide for the broader base footprint, and the Production Chain Calculator when the real question is how much material the route must carry.

Fast Answer: what should I check before rebuilding rails?

1. trace the complete rail, platform, stair, and base-piece connection to the affected machine
2. confirm the drone has a readable route and the intended priority behavior
3. simplify one crossing, merge, or elevation change before changing the whole network
4. verify the next rail reward in Clever Robotics before planning a density upgrade
5. watch the route in your own save before copying a community multi-feed layout

1. Connection and power come before routing theory

On the current live baseline, power follows connected rails, platforms, stairs, and base pieces. A line that looks like a rail-routing failure can simply be a broken connection path.

Before you change a merge, confirm:

• the generator and target machine share one continuous build path
• no platform, stair, or rail segment is visually separated
• the machine is placed on the connected route rather than beside it
• the production side is actually providing its input

Use the Power Guide for connection troubleshooting. Use the Production Chain Calculator when the route is connected but the source chain cannot meet the target.

2. Drone Smart Path and priority are verified controls

The official Base Building Basics material identifies Drone Smart Path and drone priority as logistics controls. That supports using them deliberately, but it does not turn a complicated network into a one-click answer.

The useful workflow is:

1. build one direct route first
2. observe which direction drones choose and where they wait
3. adjust path or priority for the specific branch that misbehaves
4. add the next source only after the first branch stays readable

This keeps a routing diagnosis tied to your actual base rather than a copied screenshot.

3. Single route first, then cautious multi-feed expansion

Community rail discussions show that players do run into multi-feed routing, crossings, elevation changes, and jams. Those reports are useful design prompts, not fixed engineering rules.

For a shared route, prefer these community-practice checks:

• keep the first merge visible and easy to test
• avoid hiding a crossing inside a dense machine block
• separate elevation changes from the first merge when possible
• add storage or staging only when you can explain which branch it protects
• test the changed route under the current production load before adding another feed

If the path is clean but the base is still too crowded, hand off to the Factory Layout Guide. If the crossing only fails after a new factory bank starts, re-check the target chain in the calculator.

4. Rail Modulator and Clever Robotics handoff

The current Clever Robotics reward table puts Multirail 3 and Rail Modulator 3 together at Level 5. It later puts Multirail 5 and Rail Modulator 5 together at Level 10. Treat those as verified rail-density progression handoffs.

The table alone does not justify an unsupported claim about the exact flow behavior of every modulator setup. Before a large rebuild:

• verify the reward row in the Corporation Calculator
• inspect the current build-menu tooltip for the part you unlocked
• preserve access around the corridor so an in-place upgrade is easy to inspect
• re-test the one branch that was actually failing

The Roundabout Rail Connector is a separate Clever Robotics Level 8 reward. Use it when the live build menu makes it the right routing tool for your junction; do not assume every network needs one.

5. Upgrade Drone Rails without deconstructing the whole path

Official Update 1 material says slower Drone Rails can be upgraded without first deconstructing them. That makes a staged upgrade safer than tearing down every route at once.

Use a staged pass:

1. stabilize the connected path and the source machine
2. confirm the next rail tier is unlocked
3. upgrade one stretch that is easy to observe
4. check drone pathing and deliveries again
5. move to the next stretch only after the first one stays stable

This is especially useful when the rail line also carries the power connection your machines depend on.

6. Debugging jams, crossings, and long-distance routes

When a route stops behaving as expected, do not begin with a full rebuild. Work from the nearest visible fault outward:

• No movement at all: re-check the connected build path and source production.
• Movement stalls near a merge: isolate the last branch you added, then test the simpler layout.
• Crossing feels unreliable: make the crossing visible and test it under your current save's real load.
• Long route is hard to diagnose: add one readable inspection point before you add more complexity.
• Everything looks crowded: move to the Factory Layout Guide before adding another rail tier.

What this guide deliberately does not claim

• no universal rail throughput number
• no single best multi-feed layout
• no promise that one crossing pattern works for every terrain or save
• no Update 2 preview mechanic presented as a current live rule

Related planning pages

• Production Chain Calculator
• Factory Layout Guide
• Power Guide
• Corporation Calculator