Checking mod compatibility
Own server
JAR versions, dependencies and conflictsLearn more
Select JAR files of the assembly and its version. Check the metadata requirements: downloader, Minecraft, Java, libraries and conflicts. Files remain on your device.
My game select version
We'll remember in this browser and set up where your version is available. Open link settings are more important than this choice; the Vicki versions do not change.
Result
| Mod | Version | Loader | File |
|---|
How to check mod compatibility
- Specify the exact version
Minecraft and the bootloader have different version numbers. Choose the side to run: client dependencies may differ from server ones.
- Select entire set
Add all JARs from the mods folder, including libraries. The missing library will be shown as a required dependency.
- Parse the result
Fix version errors and duplicates, then check for warnings. Unknown ranges are not considered a successful test.
Where do the requirements come from?
Fabric - from fabric.mod.json, Quilt - from quilt.mod.json, Forge and NeoForge - from META-INF/*.mods.toml. Check should be Fabric rules and NeoForge metadata.
If the build is already crashing, open Crash log review. The required Java can be checked in Table of versions.
Frequently asked questions
Is it possible to check mod compatibility before launching Minecraft?
You can check the stated requirements in JAR: versions of the game and Java, downloader, mandatory libraries, repeated IDs and conflicts. Select the full set of mods for testing.
Does the result guarantee that the build will run?
The result relates to mod authors ' metadata. Code errors and undeclared incompatibility are detected by the launch of the game and log disassembly. Unacknowledged requirements are indicated by a warning.
