Modding is easier here than in most survival games
If you’ve dealt with mod installs in other games, Vintage Story is refreshingly simple in one specific way: players don’t need to do anything. Since version 1.16, the client automatically detects and downloads the mods a server is running the moment you connect — no matching versions by hand, no separate download links to chase down. That’s a genuinely different experience to games like DayZ, where every player has to manually track down and install the exact same mod list as the server. See our guide to playing with friends for how that plays out on the joining side.
What’s left is the server owner’s side: getting mods onto the server itself. That’s what this guide covers.
Installing mods on your Vintage Story server
Two methods exist — an in-game command that pulls straight from the mod database, and a manual upload for anything it can’t find. Most people only ever need the first one.
mods.vintagestory.at/primitivesurvival, the ID is primitivesurvival. There’s no fully consistent naming standard across every mod, so if the obvious guess doesn’t work in step 2, check the mod’s Files tab for the exact name./moddb install primitivesurvival 1.22.7 fetches the release built for Vintage Story 1.22.7. Use /moddb searchcompatible primitivesurvival to see what’s available for your server’s version, and /moddb list to check what’s installed. If your host has disabled /moddb, use the manual upload in step 4..zip: the official wiki says not to extract mod zips. Upload it via SFTP or your host’s File Manager into the Mods folder inside the server’s data folder (often shown as data/Mods). The server install folder has a second Mods folder, but that one holds the three base-game mods (Essentials, Survival and Creative) and is meant to be replaced when you update the game, so your own mods don’t belong there.Install mods a few at a time rather than dumping in a full list at once — not every mod on the database is actively maintained, and if something breaks, a small batch makes it far easier to identify which one caused it. Once you’re happy with your mod list, it’s worth reviewing our server settings guide too, since heavier modpacks are exactly when settings like MaxChunkRadius start to matter for performance.
Server-side vs client-side mods
Not every mod needs to go on the server at all. Every ModDB page lists a Side (Both, Server side or Client side) that tells you where it belongs:
Install these on the server. Server-side mods only run there, and mods marked Both are sent to players automatically when they join, per the automatic sync covered above, so players don’t need to install anything themselves.
Usually visual or UI enhancements. These install only on an individual player’s own game and don’t need to touch the server at all — installing them there does nothing useful.
Common mod problems
| What you see | Likely cause | Fix |
|---|---|---|
| “Mod not found” on install | Guessed mod ID doesn’t match | Check the mod’s Files tab on ModDB for the exact ID |
| Mod installed but not working | Server not restarted, or missing dependency | Restart the server; check the mod’s listed dependencies |
| Manually uploaded mod doesn’t load | Wrong folder, extracted zip, or wrong game version | Put the unextracted .zip in the data folder’s Mods folder and use a release for your game version |
| Players get errors connecting after a mod update | Mod release doesn’t match the server’s game version, or players have a stale cached copy | Install a release made for the server’s game version; players can delete that server’s folder in ModsByServer and rejoin |
For anything not covered here — crashes, world corruption, connection errors — see our full Vintage Story server troubleshooting guide.
Vintage Story mods — common questions
Compare Vintage Story hosting providers
See our full Best Vintage Story Hosting comparison for pricing and hardware across every provider we compare, or start with a free trial server if you’re not ready to commit yet.