Vintage Story 1.22 Server Stability Issues - Vintage Story Wiki

Vintage Story 1.22 Server Stability Issues — Crash Patterns and Mitigation

The 1.22 stable release rolled out in late April 2026, and the community reaction has been split: many love the new content (rivers, boats, fishing, forge overhaul), but a meaningful minority report that 1.22 stable is materially less stable than 1.21 was at end-of-life. This page catalogs the crash patterns that admins and players have surfaced in the first few weeks, with workarounds for each. If you're considering whether to update your server now or wait for 1.22.x, read this first.

The five crash patterns reported most often

1. Look-direction crashes (client-side)

Players report the client crashing when they look in specific directions — usually in chunks containing complex modded content or newly-generated terrain near a river. The crash is not deterministic but is reproducible: walk to the same spot, look the same way, crash.

What's happening: the render pipeline trips a NullReferenceException on entities or blocks that didn't fully initialize during chunk load. The crash signature in server-crash-*.txt mentions ChunkRenderer or BlockEntityRenderer.

Mitigation:

• Set graphics → render distance lower temporarily (16-20 chunks instead of 32+).
• Avoid the problem chunk; admin-teleport through it from another player's coordinates.
• Wait for 1.22.x; the team has acknowledged this class of crash and is working on it.

2. MSI Afterburner conflict (client-side)

Specifically reported: "the game crashes if MSI Afterburner is running." Anyone running on-screen frame counters or hardware overlays should disable them before launching Vintage Story 1.22. Other observed offenders: RivaTuner Statistics Server (RTSS), Discord in-game overlay, NVIDIA ShadowPlay overlay, and any third-party FPS counter.

Why this hits 1.22 harder than 1.21: the new render pipeline for rivers and boat physics interacts poorly with overlay hooks that worked in 1.21. The game can't reject overlays gracefully, so it crashes on init.

3. World creation / world load crash

Some players cannot create a new world or load an existing one in 1.22. The game hangs at "Generating world" or "Loading world" and then crashes. This is almost always a leftover-mod problem: a mod from 1.21 that wasn't updated for 1.22 throws an exception during world init and the loader can't recover.

Mitigation:

• Move VintagestoryData/Mods/ aside (rename to Mods.disabled).
• Launch the game vanilla; verify world creation works.
• Re-add mods one by one to find the broken one.
• For the broken mod: check the mod page on the VS Mod DB for a 1.22 update.

4. Server crash after mod-installed mid-save 1.22 update

The most painful 1.22 issue. Reported by multiple admins: "I updated my server to 1.22 with mods installed, now chunks won't load." The mod that loaded in 1.21 isn't compatible with 1.22, the world references mod-added entities, the entities fail to deserialize during chunk load, and the chunk silently never loads. Players join, walk five chunks, and the server lags or crashes.

See our dedicated mod save corruption during update guide for the full recovery procedure.

5. Generic 1.22 instability (intermittent)

Several admins report "1.22 just feels less stable than 1.21" without specific reproducer steps. Random disconnects, occasional client freezes, server tick drops. This is the hardest class to debug.

Working theory in the community: the river/water physics simulation introduced in 1.22 has higher per-tick cost than the team measured during development. On mid-tier servers (4-core, mid-range CPU), the cumulative cost of physics + chunk loading + mod processing can push the server over the per-tick budget. Symptoms manifest as tick lag rather than crash.

Diagnostic: check server-main.txt for "Server is overloaded" lines. Counting them per minute gives you a stability score.

The "should I update?" decision matrix

If you must update mid-save

If you've decided to update an established modded server to 1.22:

1. Back up everything first. Copy VintagestoryData/Saves/, the entire Mods/ folder, and your serverconfig.json. If anything goes wrong, you want to roll back to this snapshot.
2. Audit your mods. For every mod in Mods/, check its page on the VS Mod DB for a 1.22 build. Any mod still on 1.21 is a risk.
3. Disable risky mods before the update. Move them out of the Mods folder. The mod will fail gracefully on world load (its blocks become "unknown") rather than crash the server.
4. Stop the server, install 1.22, restart. Watch the console for errors during first load.
5. Let one trusted player test first. Don't open to the whole community immediately. Walk around, generate new chunks, check for crashes.
6. If chunks don't load: see our mod save corruption guide.

Rolling back if 1.22 doesn't work for you

Vintage Story doesn't have a built-in downgrade path. To roll back to 1.21:

1. Stop the server.
2. Restore your pre-update VintagestoryData backup (the whole directory, not just the save).
3. Download the 1.21 server binary from your Vintage Story account → Downloads.
4. Replace the 1.22 server binary with the 1.21 one.
5. Start. Verify version with /version command in the console.

Players will need to roll back their client too. Communicate the version expectation clearly via Discord or in-game MOTD.

What to track for "is 1.22.x out yet?"

Watch /version output on community servers, the Vintage Story release announcements page on their official site, and the Mod DB for the same mod being labeled "1.22" → "1.22.1" → "1.22.2." When several popular mods land 1.22.x compatibility, you'll know the ecosystem caught up.

Related guides

• Where to find Vintage Story crash logs
• Mod save corruption during update
• 1.22 Fishing and Forge overhaul
• Server mod sync fix
• Chunk loading lag fix

Tired of mid-update server breakage? Supercraft Vintage Story hosting pins server versions per-deployment and lets you opt-in to point releases when YOU decide. Hourly backups + 14-day retention make any mid-save migration recoverable. Plans from $5.99/mo.