Echoes of Elysium Co-op and Multiplayer: Hosting a Crew Server
Echoes of Elysium is a crewed-airship game first and a solo game second. Most of the mechanics that make EoE distinct (specialized crew roles, multi-station combat, persistent ship designs) pay off the most when 2-4 players are flying the same ship across many sessions. This guide covers how multiplayer actually works, when to graduate from peer hosting to a dedicated server, and the practical config that keeps a crew running for weeks rather than collapsing after the host has a bad day.
For the in-ship co-op dynamics (roles, builds, etiquette), see our airship builder co-op crew guide. This article is the server side of the same question.
Crew Size Sweet Spot
EoE scales differently than most co-op survival games. The crew-size curve looks like this:
- Solo: playable but requires building a ship designed for one player (light, simple, weapons in pilot reach). Most of the game's interesting design space is missed.
- 2 players: the comfortable minimum. Pilot + gunner-engineer hybrid. Most of the crewed-ship mechanics work.
- 3 players: the sweet spot. Pilot, gunner, engineer. Every role is distinct, no one is bored, and combat starts feeling tactical.
- 4 players: peak coordination. Adds a dedicated scout or second gunner. The skill ceiling rises sharply.
- 5-8 players: works for fleet operations (multiple ships) or large social servers, but a single ship's roles do not subdivide cleanly past 4.
For server admins planning a public community: 4 player slots is overkill for one ship but starves a multi-ship fleet. The right cap depends entirely on whether your community will run one big crew or several small ones. See our player slots and performance guide for the hardware impact of each tier.
Peer Hosting vs Dedicated Server
Peer Hosting
One player launches the game and others join. Free, instant, and the right tool for two friends playing one Saturday session. Problems start when:
- The host has to log off. The world ends with them.
- The host's connection drops. Everyone returns to the menu.
- The host's PC is the bottleneck. Combat performance is whatever their hardware allows.
- You want to play when the host is not online.
For a one-off session with 2-3 players who are all online together, peer hosting is fine. For anything sustained, it becomes the limiting factor.
Dedicated Server
An always-on server that the crew connects to. Costs money to run (or to host) but solves every peer-host limitation. EoE dedicated servers are configured per our dedicated server setup guide; the practical considerations are below.
The "When to Switch" Threshold
Concrete signals that peer hosting has stopped working:
- Your group has tried to play three times in a row but the host was unavailable at least once.
- Combat lag is bad enough that someone has died because of it.
- Two of your players want to log in at different times during the week.
- You want to do a long-running campaign (10+ hours of cumulative progress).
- You want to add mods and have them sync reliably across the crew.
Any one of those signals points to dedicated. Two or more makes peer hosting genuinely painful.
Persistent Crews
The killer feature of a dedicated server for EoE is crew persistence. On a peer-host setup, every session re-prompts permissions, re-assigns roles, and re-shares ship access. On a properly-configured dedicated server, the crew, the ship, the discovered regions, and the role assignments all persist.
The config flags that matter:
- Persistent ship saves. The ship state (modules, damage, fuel) saves on server tick rather than on host disconnect.
- Persistent crew permissions. Who can pilot, who can fire weapons, who can edit the ship design.
- Region discovery state. Maps and waypoints stay revealed across sessions.
- Inventory persistence per player. Each crew member's personal inventory loads on rejoin.
All four are in the server configuration reference. For admin-level access (granting captain or co-captain to a returning crew member), see admin permissions and access.
Multilingual Crews
EoE has strong non-English community demand confirmed by autocomplete signals in German, Spanish, and French. For multilingual servers:
- Server name in the target language. The browser uses pattern matching; a German-named server attracts German speakers.
- MOTD in two languages. If your crew is mixed, the MOTD in both English and the secondary language reduces friction.
- Discord or external comms. EoE in-ship comms work best when the crew has voice chat. Channel-per-language Discord helps mixed-language crews avoid talking over each other.
- Region-aware hosting. A Frankfurt-located server serves DACH and Iberia better than a US-based one even if the player count is the same.
Performance Tuning for Multi-Ship or Large Crews
EoE servers scale non-linearly with ship count and crew size because physics calculations for each airship are CPU-heavy. Some practical tuning:
- RAM scales with discovered region count. A crew that has explored most of the world holds more state than a crew that has explored two regions.
- CPU scales with ship + active-projectile count. A combat session with two crewed ships and dozens of projectiles is the worst case.
- Save frequency vs server load. Frequent saves are safer but cost CPU. The default save interval is the sweet spot for most crews.
- Region ping matters. A central-Europe-hosted server for a mixed EU crew is significantly better than a US-hosted one. See our region ping planning for the actual numbers.
Mod Support on Crew Servers
Mods change the dynamics significantly. EoE supports custom content; the practical question is whether the crew runs vanilla or modded. Recommendations:
- Vanilla first, modded after. Get 10-20 hours of vanilla together before adding mods. New crews adding mods on day one struggle to separate "what is the game" from "what is the mod."
- Mod sync handled server-side. Clients download mods from the server on join. Without proper sync config, half your crew will fail to join after every mod update. See mod support and custom content for the sync setup.
- Mod compatibility lists. Some mods conflict in unobvious ways. Maintain a single canonical mod list in your community Discord.
Restart Schedule and Crew Reliability
EoE benefits from a regular restart cadence. Memory usage grows as regions, ships, and active state accumulate, and combat performance degrades on servers that have been up for many days without restart.
Recommended:
- Daily restart at low-traffic time (typically 04:00-06:00 local).
- Weekly full restart with backup verification.
- Manual restart before any major crew expedition (so a memory leak does not crash mid-combat).
See our restart schedule and maintenance guide for the scheduler setup.
When the Crew Cannot Connect
The most common multiplayer failures:
- "Connection failed" on join. Usually a version mismatch (server updated, clients did not). See connection failed fix.
- "Server not showing in browser." Browser cache issue or query port problem. See server not showing fix.
- "Joined but no ship loaded." Persistence flag issue. The crew's ship save failed to attach on join.
- "Mods failed to download." Mod sync misconfiguration; check the mod support guide above.
Cost vs Hassle
The honest math for a 3-player crew that plays 4 hours a week:
- Peer hosting: $0 but everyone needs the host online, the host's PC is the bottleneck, and 30% of sessions hit a connection or scheduling problem.
- Self-hosted dedicated on home PC: $0 software but real electricity and bandwidth costs. The host's home network becomes a single point of failure.
- Hosted dedicated: a small monthly fee, 24/7 uptime, properly-sized hardware, mod sync, automatic backups. Removes every coordination problem.
For a crew that wants to play casually over several months without thinking about infrastructure, hosted is almost always the right answer.
Ready to Host a Crew Server?
EoE crews thrive when the server is up before anyone logs in and stays up after everyone logs out. Supercraft Echoes of Elysium hosting ships with persistent ship saves, automatic backups, mod sync, multi-region hosting (so your DACH crew gets European latency and your NA crew gets American latency), and the kind of CPU tier multi-ship combat actually needs. Your captain logs in, the ship is right where they left it.