modpacks.ch by CreeperHost No ads. Just mods.

Less crash log. More playing.

Check your mods before they throw a fit.

Paste a few names into our Minecraft mod compatibility checker—or pick the JARs already in your mods folder. We’ll find a version and loader they share, check the dependencies and tell you which side needs what. Vintage Story and Hytale work here too.

JARs stay on your PC Versions and loaders matched Dependencies followed

What we actually check

First find a setup. Then make sure the files fit.

We find the Minecraft version and loader every named project publishes, then check the chosen files, where they belong and what else they need.

01

Version and loader

Minecraft loaders stay separate, and we carry the exact game version into every mod you open next. Vintage Story keeps its game version; Hytale keeps its game build.

02

The libraries it asks for

Required, optional and incompatible mods are checked for the file you picked. A library name is not enough; its version and loader need to fit too.

03

Where it belongs

We turn the file’s notes into a plain answer: client, server, both—or the server behind a Hytale world. If it doesn’t say, we don’t pretend it works everywhere.

04

Known clashes

We compare known incompatibilities with the other mods in your list. No warning does not magically mean every mod will get along.

Need the rule before the project?

Understand the failure, then check the release.

Choose a Minecraft mod loader → See what goes on the client and server → Resolve required and optional dependencies → Install Hytale mods on the world host →

Before you rely on the result

Compatibility checker questions

Can it find the Minecraft version and loader all my mods share?

Yes. Paste two to eight project names and leave the version or loader blank. We find the exact setups every matched project has released, then let you check one in detail.

Can I paste a whole mod list?

You can check up to eight projects at a time, one per line. You can also pick up to eight local JARs. Your browser reads the mod names and puts them in the same editable list. The files are never uploaded or run.

Does this checker run or inspect a mod file?

It never runs, uploads or downloads a mod. If you pick local JARs, your browser reads one small Fabric, Quilt, NeoForge or Forge metadata file—or just the filename when that fails. You can check every name before searching.

Can a Forge build be used with NeoForge, Fabric or Quilt?

Only when the project actually publishes a file for that loader and game version. We keep Forge, NeoForge, Fabric and Quilt separate because similar names do not make compatible files.

How does it decide whether a mod belongs on the client or server?

We read the install-side information for the file you picked. If the project page does not say client or server, we show “source doesn’t say.” We don’t guess.

Why does download sometimes open CurseForge or Modrinth?

Those files open on their exact CurseForge or Modrinth download page, so the creator keeps the download and those sites keep their income. A GitHub file linked by the creator can download here instead.