FIX CRASHES & LAG

Vintage Story Server Troubleshooting

Almost every Vintage Story server problem falls into one of five buckets. Find your symptom below.

Mods are the number one cause of basically everything

Before working through anything below: if you recently added, updated or removed a mod and something broke shortly after, start there rather than assuming it’s a hardware or hosting problem. Our mods guide covers dependencies and version matching, which together explain a large share of the crashes and connection failures reported here.


The five buckets

1
Connection issues

First, check the server is actually running: on a rented server, look at its status and console in the host’s panel rather than assuming a connect failure means something is broken. Also check that your game version matches the server’s exactly. If the server is up and you’re self-hosting, the most common cause is port forwarding: Vintage Story uses port 42420 by default — see the port forwarding steps in our playing with friends guide. If forwarding is set up correctly and it still fails, your connection may be on CGNAT, which blocks inbound connections entirely regardless of router configuration — a rented server sidesteps this since you’re not the one accepting the connection. If you would rather avoid port forwarding entirely, our best Vintage Story server hosting comparison covers the managed alternatives.

2
Lag

A short pause when the world autosaves (every 300 seconds by default) is normal. Beyond that, start with the basics from the official wiki’s performance advice: keep the save on an SSD and have at least 4 GB of system RAM free before starting the server. Also watch disk space, because the server shuts itself down when free space drops below DieBelowDiskSpaceMb (400 MB by default). After that, too many loaded chunks (MaxChunkRadius set too high) and entity overload from too many mobs or dropped items in one area are the two most common fixable causes, both covered with exact settings in our server settings guide.

3
Crashes

A crash that started right after installing or updating a mod is a mod problem, not a server problem — the fix is usually reinstalling the correct version or checking for a missing dependency, both covered in the mods guide linked above. If the server won’t start at all after a game update, check the .NET runtime: Vintage Story runs on .NET, not Java, and the official wiki lists .NET 10 for version 1.22.0 and newer, .NET 8 for 1.21.x and .NET 7 for 1.18.8 to 1.20.x. Self-hosted Linux servers need the matching runtime installed; on a rented server, the host picks it (some panels have a .NET version setting).

4
World corruption

Your safety net is the autosave interval plus backups: the server saves every 300 seconds by default (ServerAutoSave in servermagicnumbers.json), and stretching that interval means a crash loses more progress. See our settings guide for the details. Run /genbackup before risky changes; it makes a full copy of the save without pausing the server. The official wiki also recommends backing up before adding or removing mods and before updating the game, since removing a content mod from a save that used its blocks or items can leave them missing from the world.

5
Mod conflicts

Two mods touching the same recipe, block or system is the classic conflict pattern. Disable mods one at a time to isolate which one is responsible rather than guessing — our mods guide covers installing them a few at a time in the first place specifically to make this kind of isolation easier later.


How to actually find the cause

Guessing wastes time. These are the official tools for pinning down what’s actually happening.

/debug logticks 100

Run this on the server (as the owner, or in single player). Any server tick that takes longer than the number of milliseconds you give (100 here) gets a breakdown written to server-main.txt. Let it run for a while during the lag, then check that file in the server’s Logs folder (inside its data path; %appdata%/VintagestoryData/Logs on a default Windows install) to see what’s actually consuming time. Run the same command again to stop logging.

.debug logticks 20

The client-side equivalent, for diagnosing FPS drops rather than server lag. Use 20 if you’re usually above 60fps, or 40 if you’re usually above 30fps. Check client-main.txt in the client’s %appdata%/VintagestoryData/Logs folder afterward, and run the command again to turn logging off.

.edi

Turns on extended debug info. Type it before taking a screenshot of the frame profiler (Ctrl+F10) for extra diagnostic output — useful if you’re reporting a performance issue to a mod author or your host’s support team.


Symptom → likely cause

Symptom Likely cause Fix
Can’t connect at allPort not forwarded, or CGNATCheck port forwarding; consider a rented server if on CGNAT
Brief pause every 5 minutesNormal autosave (300 s default)Nothing — this is expected behaviour
Server shuts itself downFree disk space below 400 MB (DieBelowDiskSpaceMb)Free up disk space; keep the save on an SSD
Won’t start after a game updateWrong .NET runtime.NET 10 for 1.22+, .NET 8 for 1.21.x
General tick lag with several playersMaxChunkRadius too highLower to 8–10 in serverconfig.json
Lag concentrated in one areaEntity overload (mobs/items)Clear excess entities, lower entity tracking range
Crash right after a mod updateVersion mismatch or missing dependencyReinstall the correct mod version
Progress lost after a crashAutosave interval stretched too farKeep ServerAutoSave near 300 s; restore from backup if available

Vintage Story troubleshooting — common questions

If you’re self-hosting, this is almost always a port forwarding issue on the host’s router, not anything on your friend’s end — see the connection steps in our playing with friends guide. On a rented server, double-check the IP and port you gave them match what your host’s panel shows, and that your friend is on exactly the same game version as the server.
Some is normal: a brief pause when the world autosaves, every 5 minutes by default. It’s only worth investigating as a genuine performance issue if pauses are unusually long, or if lag persists outside of save moments. Our settings guide covers what to check.
Disable your mods, confirm the issue goes away, then re-enable them one at a time until it comes back — that isolates the culprit. It’s tedious but reliable, and it’s why we recommend installing mods gradually in the first place rather than all at once.
Sometimes, if you have a recent backup, which is why it’s worth running /genbackup before risky changes. Without a backup, recovery isn’t guaranteed. Many hosts include automatic scheduled backups as standard, which is worth checking for when comparing providers on our Vintage Story hosting comparison.
If you’ve narrowed it down to a config setting or a specific mod using the steps above, that’s usually something you can fix directly. If the server itself won’t start, or you suspect a hardware-level issue on their end, that’s worth a support ticket — and running the debug commands above first gives them something concrete to work from rather than “it’s laggy.”

Similar Posts