Vintage Story
Mods, world settings, uploading an existing world and what drives memory use.
Everything in Your panel applies. These are the Vintage Story specifics.
Startup parameters
- Release Version and Files Branch — which build to run, stable or unstable
- Max Clients
- Options — extra launch arguments
World generation settings, game rules and server configuration live in the server's config files, edited in the file manager.
Mods
Vintage Story has an active modding scene, and mods install as files in the server's mods folder — upload them through the file manager or SFTP, then restart.
Keep everything on versions built for your game version. If something fails to load, the console names the mod, which makes diagnosis unusually easy here.
Whether players need the same mods depends on the mod: some are server-side only, while anything adding blocks, items or interface changes must match on both sides. The server checks what clients have and tells them when something is missing or mismatched.
Publish your mod list somewhere so new players can set up before they try to join.
Uploading a world
Upload the save through the file manager or SFTP with the server stopped, then point the server at it. Match the game version and mod list to what the world was created with, and keep your local copy until you have seen it load.
Memory
Plans start at 2 GB for a couple of friends on a fresh world. Go higher for a larger group, a substantial mod list, or a world explored widely over many in-game years — generated terrain is what accumulates.
Upgrading a plan keeps the existing world intact.
Stable or unstable
The Files Branch setting lets you run pre-release builds. Useful if a mod you depend on has moved ahead of stable, but treat it as a testing environment rather than where your long-term world lives.