Vintage Story Server Hosting

Vintage Story mods are distributed as zip files from the official ModDB, and installation on a rented server is refreshingly plain. Download the version that matches your game build, upload it into the Mods folder with the panel file manager or SFTP, and restart from the live console.

The startup log prints every mod it loads along with its version, so a mod compiled against an older release is easy to spot and remove. Clients generally need the same mods installed locally, which is worth stating clearly in your Discord or server description.

When a world is first created, its playstyle and world config settings define the experience: season length, temporal stability and storm frequency, block gravity, hunger rate and crop growth. Those choices matter because some of them are fixed once the world is generated, so decide before you invite people in.

Anything adjustable afterwards is still yours to change through serverconfig.json and the in-game world config commands. Take a backup before you touch an established world, restart cleanly so the values load, and let the panel scheduler handle nightly restarts to keep a long-lived save responsive across in-game years.

A Vintage Story save grows steadily as players explore, mine deep, and build across chunks. Unmetered NVMe storage means that growth never runs into a quota, and automatic daily backups with ten rolling slots protect worlds that represent months of real time.

For sizing, a small group of survivors runs fine on 3 GB at $7.50 per month, ten to fifteen players on a modded world are comfortable on 6 GB, and large public servers with heavy mod lists should use 16 GB, where five cores are included. Support is available 24/7 through the portal and Discord.