Vintage Story mod dependencies and client/server requirements explained

Client, server and required do not mean the same thing

A safe installation sequence

1. 01

   Choose the target Vintage Story game version.

2. 02

   Open the mod and select a release that lists that game version.

3. 03

   Check whether that file belongs on the client, server or both.

4. 04

   Resolve every required dependency to a compatible release.

5. 05

   Open each required mod and check what it needs too.

6. 06

   Install the matching files where they belong.

7. 07

   Test a copied world and inspect both client and server logs.

Version requirements are ordered, not just labels

Vintage Story compares version numbers, including preview and development builds. Having the right mod name is not enough when another mod asks for a newer release.

An empty value or wildcard can allow any version, but a specific requirement has to match the library file itself. We keep the requested ID and matched version visible so “some version is installed” cannot hide the wrong one.

Why the exact dependency chain matters

The official project index is great for finding Vintage Story mods. Installing them still means matching releases, sides and libraries. Our API joins those pieces so we can follow the whole chain instead of stopping at a project name.

That lets us tell the difference between a matching library and one we could not verify. If the data runs out, we say so instead of deciding that every universal file must go everywhere.

For mod authors

Good modinfo saves players from broken starts and pointless server files. Keep the mod id stable, use a useful version, say which sides really need it, and list the library versions this release actually uses.

Add .modpacksch.json to the linked source repo when you want GitHub release downloads, support links or your server-host partner shown here. It gives players more useful choices without another creator dashboard.