Vintage Story Mods on a Server: The Complete Guide
Vintage Story mods come from the official ModDB. Learn how server, client and universal mods work, when friends get them, and what to check before changes.
You will need
- A Vintage Story account for each player
- Access to the official Vintage Story ModDB
- Agreement on a game version and one person responsible for the server mod list
Vintage Story mods for a shared server come from the official ModDB, and the game can offer the server’s mod list to players when they join. The part that needs care is choosing a release that matches your server, knowing which side it runs on, and keeping a recoverable copy of your world before you change the list. This guide maps those checks so your group can agree on a mod setup before anyone starts adding files. If you are still picking where the shared world should run, see our overview of how to play Vintage Story with friends.
How Vintage Story mods work on a multiplayer server#
Start with the official Vintage Story ModDB. It is the game’s own catalog for community-made mods. Vintage Story does not use Steam Workshop, and its mods are not Minecraft mods; look for Vintage Story’s own game-version, side and dependency information on each release page.
The ModDB is a place to find releases, not a guarantee that every file is right for your world. A mod may target a different game version, need another mod, or run only on one side of a multiplayer connection. Read the release details before you install it. If a page lists a newer file, that alone does not mean your server should update: your group’s game version and the rest of its mod list still matter. Mod count also does not translate into a fixed RAM amount; our guide to sizing RAM for a Vintage Story server explains what the official estimate does and does not tell you.
Before your group builds a list, agree on who will maintain it. One person should record the server version and the mods it uses, then tell the group before changing either. That small bit of coordination helps everyone join the same world with the same expectations.
For each candidate, keep a short entry with its ModDB release link, version tag, side, dependencies and the date you checked it. Note whether the group has already used that release in this world. This gives the owner something concrete to compare when an update appears, and lets another admin retrace the choice if the regular owner is away. Start with only the mods your group wants to use; a longer list creates more release pages and dependencies to review whenever the game changes.
The game’s official client requirements list Windows 10 or newer, macOS 13 or newer, and Linux; each player also needs their own Vintage Story account. There is no console version. If someone is still deciding where to buy the game or which systems it supports, our Vintage Story purchase and platform guide covers that question.
Check each mod’s side and dependencies#
A mod’s side tells you where it runs. Vintage Story’s official metadata uses Server, Client and Universal; ModDB pages may describe the last category as “both.” Universal means the mod is intended to run on both the server and client. Check the exact release page because a mod’s name or description does not tell you its side.
| Side | Where it runs | What to check |
|---|---|---|
| Server | On the dedicated server | Whether the mod requires a compatible client or other mods |
| Client | On each player’s game | Whether it is only a visual or interface change, or has other requirements |
| Universal / both | On the server and clients | Whether every required dependency is available to the server and players |
Dependencies are other mods that a release needs. The ModDB release page may list them by name and version; check that you have the required versions before starting the server. A missing dependency can prevent a mod from loading, and a dependency can itself rely on another mod. Treat the list as a small chain, not just a pile of separate downloads.
The official Modinfo reference describes side, dependency and client-requirement fields. The wiki says that page was last verified for 1.19.8, so use it to understand the terms rather than as a current compatibility list. The release page and its author’s notes are the place to check the file you plan to use.
Let the game offer server mods when friends join#
For a modded multiplayer server, friends usually do not have to install the server’s server-side and universal mods by hand. Since Vintage Story 1.16, the client can set up those mods when a player joins and accepts the server’s mod-list prompt. The game keeps them in a separate ModsByServer folder for each server, so that list stays apart from the mods a player uses in single-player.
The official Adding Mods guide documents these default locations:
| Player’s system | Server-specific mod folder |
|---|---|
| Windows | %AppData%\Roaming\VintagestoryData\ModsByServer |
| Linux | ~/.config/VintagestoryData/ModsByServer |
| macOS | ~/Library/Application Support/VintagestoryData/ModsByServer |
When a friend connects, they can accept the offered list; the game stores the downloaded files under that server’s folder. A client-only mod is different: it runs on a player’s computer and is not part of the server-side list the game offers. If a friend has a client-only add-on, they manage that on their own client.
This is the handoff to remember: the server runs its required mod list, and the joining game handles the server-side and universal downloads. If a friend is asked to copy the entire server list manually, first check whether the game version is current and whether the mod is published on the ModDB. For exact install steps on the server, use our guide to adding mods to a Vintage Story server.
Match the mod release to your server’s game version#
A mod’s version tag is a compatibility clue, not a promise that it has been tested with your exact server. The official stable-version feed listed Vintage Story 1.22.7 as the latest stable release when checked on October 9, 2026. Check the version of your own server, then compare it with the tags and notes for each release you intend to use.
Some current ModDB pages flag older 1.22 release tags as potentially outdated for 1.22.7. That warning does not prove a particular mod is broken, but it is a good reason not to assume that every “1.22” label means the same thing. Read the release notes for compatibility changes and dependencies; if the author has not confirmed your combination, keep the change small and test it on a copy of the world before you update the live server.
Keep the group’s client and server on compatible game versions as well. If the owner changes the game version or a mod, tell players what changed and give them a chance to update before the next session. A short list with clear version notes is easier to maintain than a long list where nobody knows which file changed last.
Back up your world before changing its mod list#
Make a backup before adding or removing mods, and before updating the game. The official Adding Mods guide recommends those backups. A content mod can add blocks or items to a world, so removing it later may leave the group without the content it supplied.
Before touching the live list, check that a backup exists, note when it was made, and make sure you know where to retrieve it. Keep that copy until the server has started with the new list and the group has checked the world. If a provider offers backups, read how to download or restore one and which world copy the action would replace; an advertised backup is not proof that a restore has been tested.
Change one part of the list at a time when possible. If the server no longer starts, you will have a smaller change to investigate. Keep the old mod files and your written list until the group confirms the new setup; do not update the game, remove content mods and change several dependencies in a single step.
Choose a mod workflow your group can maintain#
If the owner would rather not track ModDB releases and dependencies by hand, Game Hosting’s Vintage Story panel searches the official ModDB, installs a mod’s dependencies, copies worlds before mod changes and lets the owner choose when the game version updates. Those are documented panel features, not a measured promise about how a particular world or mod combination will perform or restore.
For a rented server, use this checklist alongside our Vintage Story server host comparison, which covers ModDB support, versions, resources and backups. If you already have a host, the installation walkthrough covers folders, dependencies and log checks.
For a home server, the same checks still apply: agree on a game version, check each mod’s side and dependencies, and keep a usable backup before changes. Whichever route you choose, the person who owns the world should keep the mod list and backup information where another trusted group admin can find them.
Quick answers
Where do Vintage Story mods come from?
The official Vintage Story ModDB is the main catalog. Review a release’s game-version tags, side, dependencies and author notes before you add it.
Do friends have to install server mods themselves?
For a modded multiplayer server, the game offers its server-side and universal mod list when they join. Client-only mods are separate.
What is the difference between server-side and client-side mods?
Server mods run on the server, client mods run on each player’s computer, and universal mods are designed for both sides. Check the mod’s own metadata.
Will a 1.22 mod work on 1.22.7?
Do not infer compatibility from a broad version label. Review the release tags and the author’s notes for your server’s version.
Does every player need an account to play with server mods?
Yes. Each player needs their own Vintage Story account and a supported PC client; Vintage Story has no console version.