StarRupture Base Building and Factory Design Guide: Surviving the Cataclysm

StarRupture is a strange beast – part survival game, part first-person shooter, part Factorio. You wake up on a hostile alien planet that periodically tries to incinerate everything you've built, and the point is to survive long enough to automate your way out of scarcity. Base building and factory design are the core of that loop, and they're also where most groups get stuck: the planet will happily punish a bad layout.

This guide collects the things I've found actually matter when building on a dedicated server with friends. It's intentionally light on specific in-game numbers (they change between patches) and heavy on the layout principles that survive updates. If you're running your server on LOW.MS, a lot of the performance advice also keeps your group's framerate happy.

Picking a spot

The single biggest quality-of-life decision in StarRupture is where you plant your first real base. A few things matter more than people think:

Resources within walking distance. Early game travel is slow. Being a 10-minute round trip from your ore deposits doesn't matter for 30 minutes of gameplay, but it compounds hard once you're hauling materials for real builds.

Flat enough terrain. The building system is prickly about uneven ground – the dreaded "Location is not stable" error triggers on bumps you can barely see. Flat areas save you an enormous amount of placement frustration. Building on foundations rather than directly on terrain is the usual workaround.

Defensible. The planet's creatures get meaner as you progress, and the cataclysmic fire waves are properly dangerous. Natural chokepoints and elevated terrain let your turret line do more work.

Cave proximity (with a caveat). Caves are valuable but there's an ongoing Early Access bug where cave entrances can be permanently blocked after a fire wave. Building near a cave is fine, building your critical infrastructure inside one is a bet.

Early structures, in the order you'll actually want them

A crafting station – not optional, you need one to progress.
Storage. Stupid amounts of storage. Sorting your inventory by type from the first day saves you hours later.
A basic enclosed shelter – sleep, respawn point, protection from weather.
A perimeter wall. Even a crude one. Creatures hit walls first, and that saves your machines.

Once those four are in place you can start thinking about factory layout.

Factory layout patterns

StarRupture's production is the classic mine → refine → manufacture pipeline, and nearly every factory design just picks a way to route materials through those three stages. A few layouts that work well:

Linear

Straight rows. Miner → belt → processor → belt → manufacturer → storage. Dead simple, easy to debug, easy to extend, plays nicely with single-lane conveyors. This is the one to pick for your first real factory – you can always upgrade to something fancier once you understand the material flows.

Hub-and-spoke

Central storage in the middle, production lines radiating outwards. Shortens conveyor runs (which is good for both performance and reliability), makes resource management easier, but can get congested as you scale.

Modular

Separate self-contained buildings for each major product type, connected by dedicated transport lines. More planning up front, but the easiest to extend and the easiest to fix when something breaks – you can work on one module without touching the others. Best choice for long-running servers because each module stays simple enough to be stable.

Conveyor belts: the single biggest performance lever

StarRupture's conveyor system is the bit that most affects server performance and is also the bit with the most Early Access bugs. A few opinions that I've yet to see backfire:

Stick to single-lane conveyors where you can. Multi-line parallel conveyors are known to be buggy – items getting stuck, rails visibly vanishing, occasional crashes. Single lanes are more reliable and also more performant on the server.

Keep runs short, with buffers. Long unbroken belts are more work for the server and harder to debug. Break a long run into segments with storage buffers between them; it isolates problems and smooths out rate mismatches.

Don't let paths overlap. Overlapping or crossing belts are a classic source of "why are items disappearing?" tickets. Keep your routing visibly separate.

Save before big conveyor rewrites. If you're about to demolish a production line and rebuild it, nudge the server to autosave first – or just wait for the next one. Complex rebuilds are when the weird conveyor bugs tend to show up.

Cataclysms and fire waves

Fire waves are StarRupture's headline disaster. They sweep across the planet on a cycle, damaging structures and spawning angry things. A few rules of thumb:

Upgrade wall materials as soon as fire-resistant options unlock. The difference between surviving a fire wave and losing a factory wing is usually material quality.
Layer your defences. Multiple wall lines, turrets with overlapping fields of fire, and repair stations pre-stocked with materials.
Go underground where you can. Critical infrastructure buried behind natural rock is a lot harder to damage than surface-built stuff.
Plan for a repair cycle – fire waves are recurring, not one-off. A base that shrugs off the first wave but has no repair plan will still bleed out over three.

Playing with friends

Dedicated server base-building is where StarRupture really comes alive, because the server stays up when you don't and roles can specialise. With 4 players on a dedicated server we generally see a loose split along the lines of mining/resources, factory design and management, defence/exploration, and tech progression – though it's worth stressing this is a loose suggestion, not a class system. Roles rotate on most servers I've seen.

Practical co-op tips that actually help:

Talk about layout before you build. Fifteen minutes of "here's where we're putting the main factory" in Discord saves hours of demolish-and-rebuild later. This is especially true once you're thinking about Update 1's bigger map – it's tempting to immediately expand outward, but it's usually worth planning the main factory's final footprint first.

One central storage hub with a clear naming convention. Labelled storage, consistent by resource type, accessible by everyone. Probably the single biggest productivity multiplier in multiplayer StarRupture.

Stagger your play sessions. One of the real benefits of a dedicated server is that Alice can grind mining while Bob's asleep, and the factory just runs. Lean into asynchronous play – it's how dedicated servers beat P2P for groups in different time zones.

Don't share the admin password. The StarRupture admin/management password is powerful – use the regular join password for your group and keep the management password to the one or two people who actually need it. See Reset passwords if it ever leaks.

What Update 1 changes for base builders

Update 1 (9 April 2026) is the first major content drop since Early Access launch. From a base-building perspective the relevant additions are:

A significantly bigger map with new unlockable zones and points of interest. More room to pick a base site, and more reason to establish forward outposts near specialised resources.
Ziplines for traversal. Actually changes how you think about base layout – longer-distance commutes between extraction sites and your main factory become cheap, which rewards more spread-out designs than the old "pack everything together" meta.
A Development Station, which opens up new progression paths inside the base.
Higher-tier ("v.2") versions of several core machines and a batch of new production buildings. If you were already near endgame pre-Update-1, you've got new things to build into.
40+ new items and recipes, which means production chains get longer and your storage will grow accordingly.
New wildlife species – some hostile, some not – meaning your perimeter defences may need a refresh depending on where you've built.

None of this breaks existing saves or factories, but it does mean a base designed for the EA-launch map may feel a bit cramped once you've explored the new zones. Worth a quiet audit of your main factory's footprint after your first Update 1 session.

Building with performance in mind

The things your base does that affect server performance are, in rough order:

Number and length of conveyor belts (biggest factor)
Multi-line conveyor complexity
Active machine count
Number of loose items sitting in the world
Number of active creatures in loaded chunks

Doing the simple-layout things above – single-lane, buffered, modular – isn't just aesthetic preference, it's actively helping your server's CPU. If you start seeing lag spikes that correlate with a specific area, that area is the one to simplify. And if simplification isn't enough, upgrading to the LOW.MS Premium CPU (Ryzen 7950X/9950X) is a real, measurable fix rather than a vague marketing bullet.

In summary

Build methodically, use foundations, keep conveyors simple, plan for fire waves, spec your server hardware to the ambitiousness of your factory, and actually talk to your group about layout before you build.

For the practical server side of it, see:

If you're just browsing and haven't got a server yet, LOW.MS StarRupture hosting starts at £6.73/mo with 10 GB RAM, DDoS protection, and automated cloud backups as standard.