Enshrouded Version Mismatch
What to do when a player's Enshrouded and your server are on different game builds: which side is behind, how to update each, and what to do with mods first.
What causes a version mismatch
When Keen release an Enshrouded update, Steam updates each player's game by itself, and the dedicated server has to follow. If the two are on different builds, the game can refuse the player.
Not every update does: Keen release some fixes for the game only, and a player on a newer game build can then still join a server on the previous build. When the builds do have to match, one side has to catch up.
GameGrid updates your server for you, so a mismatch is usually a matter of timing: your server has not been updated yet, or automatic updates are switched off on it. Restarting the server does not fetch a new build; an update is its own job.
Fix: the server is behind
1. Open your server and go to Admin.
2. Look at Game Updates. It shows the build your server is running and, when there is a newer one, Update available with its version.
3. Press Update now.
4. Your server is backed up, stopped, moved to the new build and started again. If anyone is playing it waits a few minutes first; Enshrouded cannot show them a message, so warn them in Discord.
5. The card reports the outcome by itself: 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.
If there is no Update available, your server is already on the newest build GameGrid can see, and the player's game is the one to update. From Discord, /check-update gives the same answer.
Fix: the player is behind
1. Have them let Steam update Enshrouded. Steam usually does this by itself; restarting Steam makes it check.
2. If updates are held back, in Steam: right-click Enshrouded โ Properties โ Updates, and choose to keep it updated.
3. Then start the game again fully, rather than just going back to the main menu.
Fix: you run mods
Mods patch the game's data, so a new build is the moment a mod is most likely to stop fitting. GameGrid never lets that stop your server: if a mod no longer applies, the server starts anyway (with several mods only the one that failed is left out; with one, without your mods) and logs/mod-framework.log names the one that failed.
If you would rather choose when the update happens:
1. Switch Automatically apply game updates off in Game Updates on the Admin page. The card then says the new build will not be applied on its own.
2. Check each mod's page for a version made for the new build.
3. Press Update now when your mods are ready, then restart and check the Console and logs/mod-framework.log.
Remember that while your server stays behind, players whose game has updated may not be able to join. GameGrid's own changes to the game data, the Inventory & Storage settings, are checked against each new build by GameGrid and need nothing from you.
After the update
A game update never stops GameGrid's own tools by itself: item delivery, Give, teleport, player positions and chat keep working on the new build. If the server module fails repeatedly on the new build, item delivery, Give and teleport are paused on that build only, purchases wait in the delivery queue and are handed over once it is back, and our team is alerted. See Enshrouded Game Updates on GameGrid.
Preventing version mismatches
- Leave Automatically apply game updates on unless you run mods. It is on by default.
- Tell your players in Discord when an update lands, so they update their game.
- Take a labelled manual backup before a big update as well as the automatic one: Backups โ Create Backup Now.