Enshrouded Multiplayer Server: Tips and Settings

Enshrouded has grown into one of the most popular cooperative survival games since its early access launch. Running your own dedicated server gives you full control over who joins, when the server is available, and how the world behaves. This guide covers practical tips for configuring and optimizing your Enshrouded multiplayer server.

Want your own Enshrouded server? At HostValues from €5.60 per month, online within minutes. View plans →

Server configuration basics

Enshrouded's dedicated server reads its settings from enshrouded_server.json in the server directory. Key fields include:

• name: Your server's display name in the server browser.
• userGroups: Give each user group its own password and permissions, with a different password for each group. Since Update 2 the old single password field is no longer used to set the server password; if an old file still contains one, the server turns it into a group called default.
• slotCount: The number of player slots, from 1 to 16. Set this to the number your group actually needs. More players means more world activity and higher resource usage.
• ip: Bind address. Use 0.0.0.0 to accept connections on all interfaces.
• queryPort: Default 15637 (UDP). Make sure this port is open in your firewall; Keen also refers to the ports Steam itself uses. Keen's current example configuration has no separate gamePort field.

Performance optimization

Enshrouded is CPU-intensive, especially when multiple players explore different parts of the map simultaneously. Here are practical ways to keep your server running smoothly:

• Limit simultaneous explorers: The biggest performance hit comes from players loading new terrain in different directions. Coordinate exploration to avoid everyone spreading across the map at once during the same session.
• Scheduled restarts: Memory usage tends to climb over long sessions. Restarting the server once every 12 to 24 hours clears accumulated memory and keeps performance stable. Most game panels support automated restart schedules.
• SSD storage: Enshrouded loads and saves terrain data constantly. An NVMe drive makes a noticeable difference compared to a spinning disk, especially during base building and terrain deformation.
• Allocate enough RAM: According to Keen's FAQ, the server process uses about 4.4 GB of RAM when idle plus up to 100 MB per player, and no more than 6 GB in total. For a machine that only runs the server, Keen recommends 16 GB of RAM.

World and base management

Enshrouded worlds persist between sessions. A few tips for keeping your world healthy:

• Back up regularly: Copy the savegame folder before major updates or when experimenting with settings. A corrupted save after a server crash is rare but not impossible.
• Base planning: Large bases with many crafting stations and storage containers add to the tick load. Spread crafting infrastructure across multiple smaller bases rather than one massive compound.
• Flame altar placement: Each altar extends the playable area. Place them strategically to cover the zones your group uses most without claiming more territory than needed.

Network and connection settings

• Port forwarding: If you run the server at home, forward the query port (default 15637, UDP) through your router; Keen also refers to the ports Steam itself uses. On a hosted server or VPS, ensure the firewall allows this port.
• Server not showing in browser: Verify that the queryPort is open and that no other process is using it, and enable dedicated servers in the in-game server filter. If it still does not appear, add it as a favorite in the Steam client under View > Game Servers > Favorites, using IP:queryPort.
• High latency: Choose a server location close to the majority of your players. Cross-continent connections add 100 ms or more, which is noticeable in combat.

Keeping the server updated

Enshrouded receives frequent updates during its development cycle. After each update:

1. Stop the server.
2. Update the server files through SteamCMD or your game panel's update button.
3. Back up the world save before starting with the new version.
4. Start the server and verify it loads without errors in the console log.

Players must update their game client to the same version. A version mismatch prevents connection.