SERVERCONFIG.JSON

Vintage Story Server Settings, Explained

Not every setting in serverconfig.json is worth touching. Here’s what actually matters, what to leave alone, and why.

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

MaxChunkRadiusserverconfig.json · default 12

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.

RandomBlockTicksPerChunkserverconfig.json · default 16

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.

DefaultEntityTrackingRangeservermagicnumbers.json · default 4 chunks (128 blocks)

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.

MaxClientsserverconfig.json · default 16

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.

TickTimeserverconfig.json · default 33.33 ms (30 ticks per second)

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.

ServerAutoSaveservermagicnumbers.json · default 300 seconds

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
MaxChunkRadiusserverconfig.json128–10 for busy servers
RandomBlockTicksPerChunkserverconfig.json16Small cuts only if CPU-bound
DefaultEntityTrackingRangeservermagicnumbers.json4 chunks (128 blocks)3 (96 blocks) for busy servers
MaxClientsserverconfig.json16Match your hardware, not ambition
TickTimeserverconfig.json33.33 ms (30 TPS)Never lower; 40–50 only if CPU is maxed
ServerAutoSaveservermagicnumbers.json300 sKeep near the default

World size and generation are configured separately — see our dedicated map size guide for that.


Vintage Story server settings — common questions

It can be either. Memory use rises with MaxChunkRadius, and the official wiki advises having at least 4 GB of system RAM free before starting a server and keeping the save on an SSD. If RAM usage looks fine but you still get tick lag, the CPU is the bottleneck, and the settings on this page (MaxChunkRadius, entity tracking range and, as a last resort, a higher TickTime) are the right place to look rather than adding more memory.
No. It caps players’ view distance and how much of the world stays loaded around them, not any gameplay mechanic directly. Most players won’t consciously notice a drop from 12 to 8–10 during normal play, though very long-range builds or exploration may load in slightly later.
Yes, significantly. Mods that add entities, blocks or extra logic increase the baseline workload these settings are managing, so a heavily modded server is more likely to need MaxChunkRadius and entity tracking range tuned than a vanilla one. See our mods guide for installation itself.
Double-check the JSON syntax first — a missing comma or bracket in serverconfig.json is the most common cause of a server failing to start after a manual edit. If it still won’t start, our troubleshooting guide covers this and other common startup issues.
It depends on the provider: some expose the common settings through a web control panel, while others expect direct file editing via SFTP or a file manager. Either way, the server owner can also change serverconfig.json values in-game with the /serverconfig command. If you’re still choosing a host, see our Vintage Story hosting comparison.

Similar Posts