Enshrouded Server Updates: How They Work
How Enshrouded game updates reach your server: the Game Updates card, your world, settings and mods, and what GameGrid's tools do on a new build.
Updates are applied for you
When Keen release a new Enshrouded dedicated server build, GameGrid notices it, and with automatic updates on (the default) applies it to your server for you. There is no SteamCMD to run.
Applying an update goes like this:
1. The new build is downloaded and prepared beside your current one.
2. Your server is backed up.
3. If anyone is playing, it waits a few minutes first. Enshrouded cannot show players a message, so nobody is warned in game.
4. The server is stopped cleanly (the world is saved), moved to the new build, and started again.
5. If the new build fails to start, your server is put back on the build it was running.
Restarting your server does not fetch a new build. An update is its own job.
Enshrouded 1.0 (announced by Keen Games for 15 October 2026) is a new build like any other: what to do before it and what to expect is in Enshrouded 1.0 on Your Server.
The Game Updates card
On the Admin page, Game Updates shows the build your server is running and, when there is a newer one, Update available with its version.
- Automatically apply game updates is on by default. Switch it off to stay on your current build until you choose; the card then says "Auto-update is off, so this build will not be applied on its own."
- Update now applies an available update straight away, in the steps above. The card shows that it is applying, then the build that landed, or why it failed and that your server was left on its build. You can leave the page while it runs.
From Discord, /check-update says whether an update is available.
Switching automatic updates off is worth it if you run mods: update when your mods have caught up. Otherwise leave it on, so your server is never behind your players.
What survives an update
| Survives | Notes |
|---|---|
| Your world | Updates do not touch the save |
| Your settings | Including your difficulty values and user groups |
| Your mods | Applied again on the new build where they still fit |
| The economy | Wallets, shop, kits and links are GameGrid's, not the game's |
| Backups | Untouched, and one is taken before the update |
What GameGrid's own tools do after a big update
Several Enshrouded features work by GameGrid's own server module reaching into the running game, or by GameGrid's own data for each game build. A game update never stops these features by itself. The module finds what it needs in the game by name each time the server starts, so it keeps working on a new build, and GameGrid checks it against every new build automatically on a test server of its own. If the module fails repeatedly on a new build, GameGrid pauses it on that build only and our team is alerted. So after a new build:
| Feature | What happens |
|---|---|
| Player positions, chat | Keep working |
| Item delivery, purchases, kits and Give | Keep working. If the module fails repeatedly on the new build, they are paused on that build: the Economy page says "Paused after a game update" and the live map shows the same note under it, purchases and kit claims wait in your server's delivery queue (they are not cancelled, the wait does not count towards the usual 7 days, and nobody is charged for nothing), and they are handed over by themselves once it is working again |
| Teleport | Keeps working. The landing height comes from the newest map GameGrid has published, so until the map for the new build is out, a spot the update reshaped can land a little high or low. It is paused together with Give if the module fails repeatedly on the new build |
| The map | Keeps showing the newest map it has, with a note naming the build it is from |
| Item names in the shop | Keep the previous build's names until the new list is published |
| Difficulty presets | Measured again automatically on the new build, so "Start from Hard" means the new Hard |
| Inventory & Storage settings | Applied again where the new build's data still matches, and not applied where it has moved. The Console says which |
Nothing is silently wrong: each of those states shows where you would look for it.
Mods and updates
Mods are the most likely thing to break on a new build, because they patch the game's own data.
GameGrid applies your mods before each start, to a fresh copy of the new build's data. If one no longer fits, the server starts rather than failing to start: with several mods only that one is left out, otherwise the server starts without mods. logs/mod-framework.log says which one and why.
That is deliberate: a broken mod should cost you a mod, not your server. Check each mod's page for a version that matches. See Mods on Your Enshrouded Server.
A big update is a good moment to take stock
| Do | Why |
|---|---|
| Check the Console on the first start | The server prints the settings it applied, and GameGrid's lines say what was applied |
| Re-scan your shop items | New items exist; Scan Game Items picks them up |
| Look at the Mods page | See whether your mods still apply |
| Check your settings | A new build can add settings |
Version mismatch for players
Steam updates each player's game by itself. A player whose game and your server are on different builds can often still join, because Keen release some fixes for the game only. When the game does refuse them:
1. If they are behind, have them let Steam update Enshrouded, then restart the game fully rather than just going back to the menu.
2. If your server is behind, look at Game Updates on the Admin page: with automatic updates on it is applied shortly; otherwise press Update now.
Step by step, including what to do first if you run mods: Enshrouded Version Mismatch.
Rolling back
GameGrid does not install older game builds. Keen publish one current dedicated server build, and that is what runs.
What you can roll back is your world, from a backup: Enshrouded Saves, Backups and Restore.