Vintage Story gets new versions several times a year. Updating the game itself is the easy part. On a modded server, the work is making sure your mods are ready for the new version before your world runs on it. This page covers when to update, how to check your mods, and what your players need to do.
How versions work
Versions are numbered like 1.22.7. Version 1.22 began with 1.22.0, released on 21 April 2026, and has had a series of releases since: 1.22.7 has been the current stable release since 16 August 2026.
The server and every player must run the same version. Update the server and the players together.
Before you update: check your mods
Mods are where updates go wrong. We counted how quickly the 200 most-downloaded mods on the Mod DB caught up with 1.22:
| After 1.22.0 came out | Mods with a release for 1.22 |
|---|---|
| Same day | 72 of 200 |
| Within a week | 116 of 200 |
| Within 30 days | 150 of 200 |
| By 5 November 2026 | 180 of 200 (20 still have none) |
So on the day a new version such as 1.22 lands, most popular mods do not have a release for it yet. If your server depends on mods, waiting a few weeks is normal. The game's own troubleshooting guide says to update all of your mods at the same time as the game, though some mods keep working.
To check a mod, open its Mod DB page and look at its releases. Each release lists the game versions it is tagged for. A mod with no release for the new version may still work, but you are testing it yourself.
The Mods tab on your dashboard picks the release that matches your server's game version when you install a mod.
Updating, step by step
- Take a backup on the Backups tab. The game's wiki lists updating as one of the times to back up a save. Keep the backup until the new version has run for a while.
- Check every mod as above, and download the releases built for the new version.
- Update the server. The game's wiki says to remove the old game files before installing a new version, but never the data folder, which holds your saves, settings and player data. On your Connect server everything that is yours, worlds, mods and
serverconfig.json, already lives underdata/, apart from the game's own files. - Swap the mods. Stop the server, replace the old mod files in
data/Modswith the new releases, and start it. - Tell your players to update their game, and their mods, before they join.
To update the game itself, open the Advanced tab and use Reinstall Server. It downloads the newest stable Vintage Story and replaces only the game's own files. Everything under data/, your worlds, mods and serverconfig.json, stays as it was. Start the server when the reinstall finishes.
After the update
Watch the console on the first start. Updates can involve remapping a world's blocks and items: the game's troubleshooting guide mentions a remapping step after updating, and its command list includes /fixmapping applyall, which "applies block and item remapping in order to upgrade to a new version of the game", and /bir for fixing blocks broken by changed or removed mods. If something looks wrong in the world, restore the backup you took rather than playing on.
Players
Players download the new version from the Client Area on vintagestory.at. If they update before your server does, the same page lets them download the older version to keep playing in the meantime. They also need the same mod versions as the server: see Adding mods to your server.
Related
- A player cannot join after an update: Players can't join
- Picking mods that keep up with updates: Best Vintage Story mods for a multiplayer server