How to Host a Vintage Story Dedicated Server
On this page
Vintage Story is slow, deep survival that friends want to share — but a world that only runs while the host plays means nobody else can tend the farm or finish the bloomery. A dedicated server keeps the world going for everyone.
This guide sets up a server for Vintage Story 1.22: the download and the .NET version it needs, serverconfig.json, ports, the whitelist and public listing that changed in 1.22, and mods.
Download the server and install .NET
- Download the server from your account at account.vintagestory.at — the Linux server is a separate archive; on Windows, the game folder already contains
VintagestoryServer.exe. - Install the right .NET runtime. Vintage Story 1.22 needs .NET 10; 1.21 used .NET 8. The server refuses to start on the wrong one.
- Start it once. On Linux, run
./server.sh startfrom the server folder; on Windows, runVintagestoryServer.exe. The first start creates the data folder and a new world.
Use the same version as your players: a 1.22 client cannot join a 1.21 server.
Skip the setup: HytHost Vintage Story servers let you pick any version from 1.18.15 to the latest — from €2.58/mo.
See Vintage Story plansserverconfig.json: the settings that matter
The settings file is serverconfig.json in the data folder (%AppData%\VintagestoryData on Windows, ~/.config/VintagestoryData on Linux). Changes apply after a restart.
| Setting | What it does |
|---|---|
ServerName | The name players see |
Port | 42420 by default |
MaxClients | Player slots, 16 by default |
Password | Join password; empty means none |
WhitelistMode | 2 whitelist on, 1 off, 0 default (on for a dedicated server) |
AdvertiseServer | true lists the server publicly |
WorldConfig | Seed, world name and play style for a new world |
The full command list for running the server is in Vintage Story server commands.
Whitelist and public listing in 1.22
Since 1.22 a new server is invite-only out of the box: it is whitelisted and does not appear in the public server list. Two ways forward:
- A private server for friends: keep the whitelist and add each player with
/player Name whitelist on. That works straight away, without a restart. - A public server: run
/serverconfig advertise onto list it and/serverconfig whitelistmode offto let anyone join — then set a password or keep an eye on who joins.
Ports and how players join
Forward port 42420 for both TCP and UDP on your router and firewall — UDP has been needed since 1.20. Players add the server in the game's multiplayer menu with your public IP (add :port if you changed it).
Hosting at home means your PC has to stay on whenever someone wants to play, and your home IP is visible to everyone who joins.
Adding mods
- Find mods on the official database, mods.vintagestory.at, and check that each supports your game version.
- Install them by putting the zip files in the
Modsfolder inside the data folder while the server is stopped — not in the server's ownModsfolder, which is reserved for the base game. Or run/moddb install modidfrom the console. - Restart the server.
When players join, the game offers to download the server's mods. Only mods marked as server-side or universal are downloaded automatically; client-side mods have to be installed by each player.
How much RAM a Vintage Story server needs
The official guideline is 1 GB plus about 300 MB per player, with four CPU threads recommended. Mods and exploring far from spawn add to that:
| Setup | RAM |
|---|---|
| 2–3 players, no mods | 2 GB |
| A group with mods | 4–6 GB |
| Large mod packs | 8 GB |
Vintage Story server hosting on HytHost
- Order and pick the version. On Vintage Story hosting, choose a plan and the game version — the latest, or any stable version back to 1.18.15. The right .NET runtime is set up for you.
- Use the Startup tab. It holds the server name, slots, password, seed, play style and the whitelist switch. The panel writes these into
serverconfig.jsonat every start, so change them there rather than with/serverconfig— those would be undone at the next restart. Adding players with/player Name whitelist onworks as usual. - Add mods by uploading zips to
data/Mods, or list ModDB mod IDs in the Startup tab; those are installed on the next reinstall. - Join with the address and port shown in your panel.
Your files live in the data folder. Moving an existing world over is covered in uploading your world to a game server.
Any version from 1.18.15 up, ModDB installs and automatic backups — Vintage Story hosting from €2.58/mo.
See Vintage Story plansFrequently asked questions
The server software comes with the game at no extra cost; you download it from your Vintage Story account. Hosting it means either your own PC kept on or a rented server.
42420 by default, on both TCP and UDP. UDP has been required since version 1.20.
Since 1.22 a new server is whitelisted. Add them with /player Name whitelist on, or turn the whitelist off. Also check that everyone runs the same game version and that port 42420 is open for TCP and UDP.
The game offers to download them on join, but only mods marked as server-side or universal are downloaded automatically. Client-side mods have to be installed by each player.
The official guideline is 1 GB plus about 300 MB per player. In practice 2 GB suits a few players without mods, 4 to 6 GB a modded group, and 8 GB large mod packs.
Keep your Vintage Story world turning
HytHost Vintage Story hosting runs any version from 1.18.15, installs ModDB mods and backs your world up automatically — from €2.58/mo.
Live chat 8 AM – 11 PM (Chișinău time) · tickets answered during business hoursWas this guide helpful?