Skip to content
GameVault

Common Forge and NeoForge errors

How to read Forge and NeoForge loading errors such as ModLoadingException and "Failed to create mod instance", and how to fix them.

Last verified

The problem

How to read Forge and NeoForge loading errors such as ModLoadingException and "Failed to create mod instance", and how to fix them.

Possible causes

  • One mod crashed while Forge or NeoForge was setting it up.
  • Missing or wrong-version dependencies.
  • A mod for a different Minecraft version.
  • A broken config file written by an earlier crash.

How to identify the cause

  • The error screen and crash report list each failed mod with "Failure message". Read the first one; later failures are often side effects.
  • Lines starting with Caused by explain the actual error.

Step-by-step fix

  1. Note the first mod listed with a failure message.
  2. Update it to the newest build for your Minecraft and loader version.
  3. Install or update dependencies it reports.
  4. If the error mentions a config file, delete that one file from config (back it up first) and let the mod recreate it.
  5. Update Forge or NeoForge itself to the newest build for your Minecraft version, unless your modpack pins a specific build.

If that did not work

  • Check the mod's issue tracker for the error message; many have known fixes or workarounds.

Affected versions

Forge and NeoForge, all versions.

Frequently asked questions

What is the difference between Forge and NeoForge?

NeoForge is a fork of Forge created in 2023. Many mods moved to NeoForge for 1.20.2 and newer. See the loader comparison.