Minecraft Java Mods Won't Launch? Check Versions, Loader and Dependencies

When a modded game won't launch, back up the instance and world first, then check the Minecraft version, mod loader, mod version and required dependencies. Two files ending in .jar aren't necessarily compatible. This guide is for Java Edition; Bedrock add-ons use a different system.

Preserve the evidence

Close the game and copy the affected instance's mods, config, saves and logs folders where present. Don't wipe the entire game directory or test mod removal on your only world.

In the affected instance's game directory, inspect logs/latest.log and, if created, the current file in crash-reports. A third-party launcher may give every instance its own directory. No crash report doesn't mean no loading error.

Check the four matches

• Minecraft version: use the version range stated by each mod author, not a similar-looking filename.
• Loader: install a mod for the loader it explicitly supports. Fabric, Forge and NeoForge aren't automatically interchangeable.
• Dependencies: install the required libraries and compatible versions listed by the author; not every mod needs the same library.
• Duplicates and runtime: remove duplicate versions only after backup. If a custom Java path is configured, check the game and loader's runtime requirements; don't assume the newest Java fixes everything.

For a modpack, follow its author’s version list rather than updating everything at once.

A new launcher installation is not automatically an isolated mods folder. In Minecraft Launcher, open Java Edition → Installations and create or edit the test installation; set its Game Directory to a new separate folder before launching. Select the intended loader profile and confirm its directory before copying test mods. The separate folder also has its own saves and config; never point it at the only original world.

Read the log, then isolate

Look for missing dependency, version mismatch or loading failure messages and record the mod IDs and required versions. A named mod is a lead, not automatic proof it is the sole cause. An exit code alone, including code 1, doesn't prove an out-of-memory error. Before sharing logs, inspect them for account details, server addresses and personal paths.

Create a separate test instance with the same game version and loader, and make sure it starts with an empty test world. Add the target mod and its required dependencies, then add other mods in batches while keeping dependencies together. Record what changed each time. For author support, provide versions, mod list, reproduction steps and the relevant full log.

The cited Fabric documentation is an example for that loader; check other loaders' own documentation. We have not installed these mods or reproduced your crash.

Sources

Fabric: Installing Mods · Fabric: Crash Reports · Fabric: Uploading Logs Forge Forums: Support FAQ