Web Analytics Made Easy - Statcounter
Server Tools

Tools / Vintage Story

Vintage Story Modpack Doctor

Drop your Mods folder and find out which mods have a release for the game version you want to run, before you upgrade rather than after. Built for the 1.22 move to the .NET 10 runtime, which stops compiled mods loading until their authors rebuild them. The zips are read in your browser and never uploaded.

1 · Read your Mods folder

Drop your Mods folder here

or choose it below. Files stay on your machine.

2 · Check it against a game version

Leave blank for the current stable release.

Filled in automatically from the folder above. You can also paste a list yourself, one modid@version per line. Text only, max 100 KB and 250 mods. Mod data comes from mods.vintagestory.at and is cached.

Want this on a real server? Supercraft hosts Vintage Story →

What actually breaks on 1.22

Vintage Story 1.22 requires the .NET 10 Desktop Runtime, up from .NET 8 on the 1.21 line. That is the change that matters for a modded server. A mod is one of two things:

  • Content or theme mods are JSON and assets. The runtime change does not touch them, and they usually carry across a version bump untouched.
  • Code mods ship a compiled .dll. One built against .NET 8 will not load on 1.22 until its author rebuilds it. No amount of editing config on your side fixes that; it needs a new release.

This is why the folder drop is worth using rather than pasting a list. The Mod DB can tell us which versions an author has tagged, but only reading your actual zips reveals which of your mods carry a binary, and that is the set at risk.

Three grades, not two

Each release on the Mod DB carries tags naming the exact game versions its author supports. We report against those honestly rather than collapsing them to yes/no:

  • Declared — your target version is in the release's own tag list. The author has said this works.
  • Likely — tagged for the same minor line but not this exact patch. Vintage Story patch releases rarely break mods and authors routinely lag a patch behind, so this almost always runs. Nobody has promised it.
  • No release — nothing in that minor line at all. This is the one that stops a server booting.

Anything we cannot look up is reported as unverified rather than assumed fine. A wrong "compatible" here is worse than no answer: it gets a 500-hour world onto a server that will not start.

The upgrade manifest

The result includes a plain-text plan you can keep: which mods to update and to what version, with download links; which have no compatible release and need a decision; which are fine as they are; and which could not be verified. Take a world backup before acting on it, and verify the backup restores rather than merely that it was written.

Running Vintage Story on a managed server

On a managed Vintage Story server the version bump is staged: a snapshot is taken first, so an upgrade that surprises you is a restore rather than a rebuild.

Check a world for damage → · Build a worldconfig → · What changed in 1.22 →

Mod zips are read in your browser, never uploaded Versions from the official Mod DB, not guessed Declared / likely / no release - graded honestly

Frequently asked questions

Why did my Vintage Story mods stop working on 1.22?

Vintage Story 1.22 runs on the .NET 10 Desktop Runtime, up from .NET 8 in the 1.21 line. Any mod that ships a pre-compiled binary built against .NET 8 has to be rebuilt by its author before it will load on 1.22. Content-only mods, which are JSON and assets rather than compiled code, are not affected by that change and usually carry straight over.

How do I know if a Vintage Story mod supports my game version?

Every release on the official Mod DB carries tags listing the exact game versions the author says it supports. A release tagged 1.22.7 is declared compatible with 1.22.7. A release tagged only through 1.22.5 will very probably still run on 1.22.7, because patch releases within a minor line rarely break mods, but the author has not tested it. A mod with no 1.22.x release at all is the one that will stop your server booting.

Does this upload my mods?

No. The zips are opened in your browser and only the metadata read out of each modinfo.json (mod id, version, type, side, declared game dependency, and whether the zip contains a .dll) is sent, so the compatibility lookup can run. A Mods folder is often hundreds of megabytes and sometimes holds private config; none of that needs to leave your machine to answer whether the upgrade is safe.

What should I do about a mod with no compatible release?

Do not upgrade the server yet. Check the mod's page for a pre-release or a fork, ask the author whether a rebuild is planned, or decide to run without it and accept losing whatever it added to the world. Upgrading first and discovering afterwards is how people end up with a long-lived world on a server that will not start.

This tool: v1.9 · updated 18 Sep 2026