Star Rupture Multiplayer & Co-op Guide
Star Rupture supports co-op, while its dedicated-server feature is still marked experimental. Treat a hosted world like a small operations project: agree who owns the save, test one external join, and keep the build and endpoint written down for the group.
Choose the session model
| Model | Good for | What to plan |
|---|---|---|
| In-game host | A short session with the owner present | The host's availability, local network path, and a clean handoff if the group outgrows it. |
| Dedicated server | A persistent shared world | Experimental tooling, process supervision, backups, updates, and an external join test. |
| Managed host | A group that wants the world online without maintaining the machine | Panel access, current package, save access, backups, region, and the provider's actual support boundary. |
First-session checklist
- Choose a world owner and a second person who can operate the server.
- Record the game build, server package, external address, and chosen port.
- Use the official launch example as the starting point:
StarRuptureServerEOS.exe -Log -port=7777. - Allow and forward the same port where self-hosting, then test from outside the host network.
- Join with one trusted player, change something harmless, stop cleanly, and confirm the change survives a restart.
- Invite the full crew only after the save and endpoint checks pass.
Coordinate a shared factory
- Give each player ownership of a module, such as inputs, processing, storage, or exploration.
- Keep one shared note with current recipes, open tasks, and anything changed after an update.
- Do large construction or save migrations when the fewest players are online.
- Do not assume every client can repair a server-side configuration problem; keep an operator available.
When somebody cannot join
Check in this order: client/server build, running process, endpoint and port, host firewall/router, then EOS or authentication symptoms. Compare a local-network test with an external test. If the server is reachable but the world is wrong, stop investigating networking and follow the restart/persistence guide.
Save handoff and host changes
Never overwrite the production save blindly. Stop the old process, copy the source save, place it in the target package's documented data location, launch a test copy, and verify world identity and a new save. Use the local-to-dedicated transfer guide and the backup guide.
Official references
The official support article calls dedicated servers experimental and documents the EOS executable, launch example, and same-account caveat. Read it alongside the official announcement feed before promising a feature to your crew.
Related guides
See managed Star Rupture hosting for persistent co-op worlds.