NEW 📢 Limited launch offer: up to 70% off your first month on every game!See plans

Vintage Story mods do not load on your server

Vintage StoryUpdated Oct 30, 20265 min read

When a mod does not load on a Vintage Story server, the most likely cause is a mod that was not made for the server's game version. The server can still start with a mod disabled, so check the Console line Found ... mods (... disabled) after a start, then install the mod again from the Modding tab, which only offers releases built for your server's version.

How do I see which mods loaded?

  1. Open your server in the panel and click the Console tab.
  2. Restart the server and wait for it to be Online.
  3. Look for the line that counts the mods, for example Found 5 mods (0 disabled), and the line after it that names them, Mods, sorted by dependency:. Use the Search the console icon and type mods to find them.
  4. If the number of disabled mods is above 0, or your mod is not named, read the Warnings and Errors filters for the lines about it.

Why is my mod switched off?

It was built for another game version

Vintage Story mods name the game version they are made for, and the official troubleshooting guide says a mod not updated for the game version you play is a common cause of problems, for example a 1.21 mod on a 1.22 server. This happens most with zips uploaded by hand, or after the server moved to a new minor version.

Fix: open the Modding tab, click Installed, Uninstall the old file, then find the mod under Browse and click Install. The panel only offers releases built for your server's version. If none exists, the mod has not been updated yet: wait for its author, or keep the server on the older version (How to update your Vintage Story server).

A mod it needs is missing

Mods often need a library mod. When you install from the Mods tab, the panel adds the needed mods for you. A zip uploaded by hand brings nothing with it.

Fix: install the mod from the Mods tab instead, or install the missing mod the error names.

The server has not restarted since the install

Mods load when the server starts. Restart it from the Console tab after every install, update or removal.

Why did the panel refuse to install a mod?

The panel checks first and changes nothing when it refuses. The message says why, for example:

  • The release is "not built for Vintage Story" your version, "so the game would switch it off": pick a release for your version under Choose a version in the mod's menu, or wait for one.
  • The mod "needs" another mod that has no release for your version: it cannot run on your server yet.
  • A file of the same name "is already on this server and was not installed from this page": remove that file in Files first.
  • "We could not tell which Vintage Story version this server runs": the panel cannot match mods to it, so installing is paused. Contact support and we will sort it out.

Why did the reinstall for the ModDB mods list fail?

The reinstall that fetches the ModDB mods list stops at the first mod it cannot fetch: an id that is not on the ModDB, or a mod with no release for your game version. The mods you had stay in place. The server page then shows Reinstall failed with Open a ticket: your files are still there, and support sees which mod stopped it and gets the server running again. Before a reinstall, open mods.vintagestory.at/ followed by each id in your browser to check the mod exists and has a release for your game version.

More on mods: How to add mods to your Vintage Story server. Other problems: Vintage Story server problems and fixes.

Already hosting it somewhere else? Move your server to us

OUR LATEST BLOGS