serverconfig.json and servermagicnumbers.json
Most day-to-day settings — world name, password, player count, chunk radius — live in serverconfig.json inside your server’s data folder. A smaller number of deeper performance settings, including entity tracking range and the autosave interval, live in a separate file called servermagicnumbers.json, which the official wiki describes as risky tuning parameters that almost never need changing. Edit either file only while the server is stopped; while it’s running, use the in-game /serverconfig command instead. If you set up your server using a custom --dataPath as recommended in our guide to playing with friends, both files live inside that folder rather than mixed in with your single-player settings. If you have not chosen a host yet, see our best Vintage Story server hosting comparison.
If you’re running mods, this is doubly worth reading — heavier modpacks are exactly when these settings start to matter, as covered in our mods guide.
The four settings worth adjusting
The highest view distance (in chunks) any player may have, which decides how much of the world the server keeps loaded around each player. The official config notes that higher values need more RAM, and the wiki’s performance advice is to reduce it to 10 or lower when a server struggles. Dropping it to 8–10 reduces load on busy servers, and most players won’t consciously notice the difference in view distance during normal play. If you’re seeing tick lag with several players spread across the map, this is the first setting to touch.
How many random block ticks each chunk gets, the system behind slow natural changes; the official config’s own example is that a higher value makes grass grow back faster. Lowering it a little trims background work on a busy server at the cost of those changes happening more slowly, while raising it adds load. Random ticks only run near players: BlockTickChunkRange (default 4 chunks, about 128 blocks) sets that radius.
How far from a player, in chunks, entities such as animals and other players are tracked and kept updated; it is capped by each player’s view distance. The value is a chunk count, not blocks: the wiki’s performance tip is to set it to 3, which cuts the range from 128 to 96 blocks and saves work on creatures further away, without players noticing anything different up close.
Your player cap. Set it to what your hardware can genuinely support smoothly rather than what sounds impressive — an overloaded server that struggles at 20 players is a worse experience than a well-tuned one that holds steady at 10. Our troubleshooting guide covers the symptoms of a server that’s genuinely over capacity.
Two settings people get the wrong way round
These two are often tweaked in the wrong direction, which causes more problems than it solves.
The target number of milliseconds between server ticks. Lowering it sounds like it should improve responsiveness, but it asks the server for more than 30 ticks per second, which a busy server can’t keep up with, so it produces tick lag rather than fixing it. Going the other way is a deliberate trade: the official wiki’s performance advice for a struggling server is to set it to 40 or 50, which lowers the server from 30 to 25 or 20 ticks per second in exchange for CPU headroom. Leave it at the default unless the CPU is genuinely maxed out.
The number of seconds between autosaves of the world, so by default the server saves every 5 minutes. It’s tempting to stretch this out to avoid the short pause while a save runs, but the interval is also how much progress you lose if the server crashes. Keep it near the default, and use /autosavenow or /genbackup (a full copy of the save that runs without pausing the server) before risky changes.
All settings at a glance
| Setting | File | Default | Recommended |
|---|---|---|---|
MaxChunkRadius | serverconfig.json | 12 | 8–10 for busy servers |
RandomBlockTicksPerChunk | serverconfig.json | 16 | Small cuts only if CPU-bound |
DefaultEntityTrackingRange | servermagicnumbers.json | 4 chunks (128 blocks) | 3 (96 blocks) for busy servers |
MaxClients | serverconfig.json | 16 | Match your hardware, not ambition |
TickTime | serverconfig.json | 33.33 ms (30 TPS) | Never lower; 40–50 only if CPU is maxed |
ServerAutoSave | servermagicnumbers.json | 300 s | Keep near the default |
World size and generation are configured separately — see our dedicated map size guide for that.
Vintage Story server settings — common questions
/serverconfig command. If you’re still choosing a host, see our Vintage Story hosting comparison.