EnshroudedTroubleshootingPlayers can only join a server that runs the same Enshrouded build as their game. Steam updates players right away, and your server checks for a new build…
Players can only join a server that runs the same Enshrouded build as their game. Steam updates players right away, and your server checks for a new build about every 10 minutes, then moves onto it by itself the next time nobody is on. To update straight away, restart it from your dashboard. Enshrouded 1.0 came out on October 15, 2026, and every patch since, hotfixes included, takes exactly the same path.
Enshrouded only lets a player join a server on the same build as their own game. When Keen ships a patch, Steam updates players within minutes, so for a short while the server can be one build behind and players see a version mismatch. That happens on every host and on self-hosted servers too.
About every 10 minutes we check Steam for a new Enshrouded server build.
When your server is behind, its card shows a purple download arrow next to the status. Hover it and it reads New update available and "Restart your server to apply the latest patch."
Once nobody has been on for 15 minutes, the server restarts onto the new build by itself. It never restarts with a player on, and it saves the world on the way down.
A stopped or sleeping server comes back on the newest build the next time it starts.
When a player reports a version mismatch:

Have them update the game: in Steam, open Downloads and let the Enshrouded update finish, or restart Steam to force it through.
If your card shows New update available, press and hold Restart until the ring completes. The server saves the world, then starts on the new build.
No download arrow yet, and the patch is only minutes old? Our check may not have seen it. Wait about 10 minutes, then restart.
If everyone got in except one player, their game is the one behind. Matching builds is Enshrouded's rule, so no server setting lets an outdated player in.
1.0 was an update to the same game, so your server moved to it like any other patch: by itself once it was empty, or when you restarted it. Keen's hotfixes since then work the same way.
Nothing on our side touches your world during an update: the server restarts onto the new build with the same world files, and your Backups list keeps the backups you took before 1.0.
1.0 changed how a world is saved. The first time the 1.0 server loads a world from before 1.0, the game converts it to the new format: the world is now savegame/world0.ksd, and the old files are kept in savegame/migrated.
Keen's 1.0 notes say the skill tree resets the first time a player loads an existing save, so every player spends their skill points again. Characters live on each player's PC, so that happens on their side.
Want a fresh world for 1.0? Press New World on the expanded Backups card, then press and hold Start New World; it powers a running server down for you. It deletes the world only and keeps your settings and role passwords, and your old world is saved as a backup first: Start a new world and pick its seed.
PlayStation 5 gets Enshrouded at 1.0 too. Haptic's Enshrouded servers are for the PC (Steam) version today, and PS5 support is coming: 1.0 lets PS5 players join dedicated servers through Keen's own online service, and we're setting Haptic up with Keen for it. We'll announce it when PS5 groups can join. PC and PS5 players can't share one server at 1.0, because the game has no crossplay yet.
There is no way to keep an Enshrouded server on an older build or to switch updates off. Players can only join a server on the same build as their game, and Steam updates players automatically, so a server held back would lock everyone out. Backups hold your world, not the game version, so restoring one does not take the server back to an older build either.
Reach us on Discord or at support@haptic.gg. Include your server name and a screenshot of the message the player sees.