A shared Vintage Story world of temporal storms, seasons and hard-won craftsmanship, with everything from serverconfig.json to roles in your hands.

Select from our wide range of optimized game servers. Each server is configured for maximum performance and comes with DDoS protection.






Compare recommended use, plan hardware and monthly prices.
| Plan | Recommended for | Hardware | Monthly price |
|---|---|---|---|
| Silver 6GB | 2–10 players, vanilla or light modsThe smallest plan for this game; comfortable for friend groups at default view distance. | 4 vCore Ryzen 9950X · 6 GB DDR5 6000MHz · 60 GB NVMe SSD Samsung 990 PRO | ₺345.00/mo |
| Gold 8GB | 10–16 players or content modsRecommended for full servers at the default 16-player cap or a few content mods. | 4 vCore Ryzen 9950X · 8 GB DDR5 6000MHz · 70 GB NVMe SSD Samsung 990 PRO | ₺440.00/mo |
| Platinum 10GB | 16–25 players, modded communityRoom for the loaded area on servers with a raised MaxClients and players spread across the map. | 4 vCore Ryzen 9950X · 10 GB DDR5 6000MHz · 100 GB NVMe SSD Samsung 990 PRO | ₺530.00/mo |
| Diamond 12GB | 25–35 players, large mod listFor community servers with widely explored worlds and heavy content mods. | 4 vCore Ryzen 9950X · 12 GB DDR5 6000MHz · 110 GB NVMe SSD Samsung 990 PRO | ₺617.50/mo |
| Emerald 16GB | 35–50 players, public server6 vCores and 16 GB, a safe level for heavy world generation and busy sessions. | 6 vCore Ryzen 9950X · 16 GB DDR5 6000MHz · 120 GB NVMe SSD Samsung 990 PRO | ₺840.00/mo |
| Xtreme 32GB | 50+ players or a very heavy modpack12 vCores and 32 GB; more than most servers need, sensible for big public projects. | 12 vCore Ryzen 9950X · 32 GB DDR5 6000MHz · 200 GB NVMe SSD Samsung 990 PRO | ₺1520.00/mo |
Made for the parts of a Vintage Story server that take real effort: one config file, the role system, mods and a growing save.
Edit ServerName, Password, MaxClients, AllowPvP, AllowFireSpread and MaxChunkRadius in the file manager and apply them with a restart.
Use roles such as suplayer, sumod and admin to decide who can build and who moderates, and lock the server to known players with the whitelist.
Upload .zip mods from mods.vintagestory.at to the Mods folder over SFTP; server-side mods ask nothing of your players.
Upload the .vcdbs save of a world you created in single-player to the Saves folder, point WorldConfig at it and it loads with all its settings.
MaxChunkRadius caps how far players can load the world; tuning it on busy servers cuts memory and CPU load directly.
As players push into new land, the server generates terrain, ore deposits and climate on the fly, and the Ryzen 9 9950X with NVMe keeps those moments smooth.
Vintage Story server hosting at TheCrewHost starts at $8.63 per month (₺345.00), on plans beginning at 6 GB of RAM. Your server installs automatically after payment and runs 24/7 on a Ryzen 9 9950X with NVMe SSD storage in İstanbul, giving players in Türkiye low latency. Set the player cap, password, PvP and the view distance ceiling in serverconfig.json, and upload mods from the ModDB into the Mods folder. You can also build a world in single-player with exactly the settings you want, move its .vcdbs file to the server and work your way from copper to iron with friends.
Vintage Story is a survival game built on a deep crafting chain that starts with stone tools and runs through pottery, copper casting, bronze alloys and eventually ironworking. Seasons turn, crops need weeks of in-game time to ripen, realistic geology makes prospecting an actual investigation and temporal storms bring danger on a regular rhythm. That progression takes weeks, and it is far more rewarding in a shared world.
In a world hosted on a friend's PC, the crops, the pots firing in the kiln and everything you set up only exist while that friend is playing. On a dedicated server the world is open to everyone at any hour; one player can work the mine during the day while another picks up the smithing in the evening.
Your own server also lets you shape the community. Run a password-protected world for friends only, give newcomers a visitor role until they earn trust, or turn on AdvertiseServer to appear in the public list and grow a community of your own.
Nearly every Vintage Story server setting lives in serverconfig.json in the data folder. ServerName sets the name, Port holds the connection port, which defaults to 42420, and MaxClients sets the concurrent player cap. MaxClients defaults to 16, so a bigger community needs it raised. Password locks the server, and AdvertiseServer puts it on the public server list.
Settings that shape gameplay sit here too. AllowPvP controls player damage and AllowFireSpread decides whether fire spreads. MaxChunkRadius caps how far players can load the world and defaults to 12; it is one of the most effective levers you have over server load.
The world itself is defined in the WorldConfig block: Seed, WorldName, SaveFileLocation and PlayStyle, plus a WorldConfiguration section holding dozens of options such as temporal storm frequency, death punishment and world size. The easiest route is to create the world in single-player with the options you want and upload its .vcdbs file to the server.
For a vanilla group of up to 10 players, 6 GB is a comfortable start. Two big factors drive memory use in Vintage Story: how many world chunks are loaded at once and which mods are installed. Each player keeps an area the size of MaxChunkRadius loaded around them, so as players spread across the map, the loaded area and the memory needed grow together.
Mods are the second factor. Content mods that add blocks, items and creatures noticeably raise both startup time and memory use. A modded community at the default cap of 16 is healthier on 8–10 GB, and servers above 25 players running large mod lists do better with 12 GB or more.
On the CPU side, world generation is the heaviest job. When players head into land nobody has visited, the server generates terrain, climate and ore deposits on the spot. A high-clocked Ryzen 9 9950X cuts the stutter in those moments, and NVMe storage keeps the growing .vcdbs save quick to read and write.
Vintage Story handles permissions through roles. The defaults include survival roles such as suvisitor, limitedsuplayer, suplayer, sumod and admin, plus their creative-mode counterparts. DefaultRoleCode in serverconfig.json decides which role newcomers get, and it is suplayer out of the box. On community servers, starting new players on a limited role and promoting them once they have proven themselves is an effective defense against griefers.
To make yourself an admin, run /op playername in the server console; it does the same job as /player playername role admin. You can also add that command to the StartupCommands field in serverconfig.json so it runs on every boot.
For a whitelist, use the WhitelistMode setting and add players with /player playername whitelist on. There is /kick and /ban for people who break the rules and /unban for those you forgive. /autosavenow forces an immediate save; running it before a big change and then taking a panel backup is a habit worth keeping.
The official home for Vintage Story mods is the ModDB at mods.vintagestory.at. Mods usually come as .zip files and go into the Mods folder in the server's data directory as they are, without extracting. Restart the server and the console lists every mod it loaded.
Each mod declares a side value in its modinfo.json. Mods marked Server run only on the server and require nothing from players. Universal, the default, covers mods that must exist on both the server and the player's side; most content mods that add new blocks and items fall into this group. Client mods run only on a player's PC, typically interface or visual tweaks.
Watch version compatibility when adding mods. The modding API can change between major Vintage Story releases, so check which game version a mod supports on its ModDB page. Before updating the game, confirm that new mod versions are out and back up your saves together with the Mods folder for a smooth transition.
A small vanilla group can start on Silver 6GB; communities running content mods or pushing the 16-player default should go for Gold or Platinum.
Once payment is confirmed the Vintage Story server installs and appears at gamepanel.hostingmerkezi.net; the first boot creates serverconfig.json and a default world.
Optionally create a world in single-player with your preferred options, upload its .vcdbs file to Saves over SFTP and point SaveFileLocation in WorldConfig at it.
Stop the server and set ServerName, Password, MaxClients, AllowPvP and MaxChunkRadius; turn on AdvertiseServer if you want a spot in the public list.
Drop the .zip mods from the ModDB into the Mods folder, start the server and run /op playername in the console to take the admin role.
Players add a server under Multiplayer and enter the IP:port from your panel, or find it in the public list, and type the password if one is set.
The questions people ask before renting a Vintage Story server: RAM, roles, mods, moving worlds and connecting.
Our İstanbul datacenter runs on Ryzen 9 hardware, delivering low latency to players in Türkiye and good connectivity to Europe, the Middle East and the Caucasus.
Turkey
Everything your project needs — from game servers to VPS, dedicated servers, web hosting and Discord bot hosting.
Connect with our community of gamers and developers
Get instant support, share experiences, and stay updated with the latest news