Fix "Found duplicate mods" and two copies of one mod
Two jars of the same mod in one mods folder usually don’t stop the game on current loaders. The loader keeps one copy and starts, so the trouble shows up later: you changed or updated the mod, and the game runs the other copy.
With two copies of the same mod jar in the mods folder of a 1.21.1 dev server:
- NeoForge 21.1 kept one and started. The only trace is at debug level:
Found 3 mods for first modid examplemod, selecting most recent based on version data(three: the two jars and the dev build), thenSelected file examplemod-1.0.0 (1).jar for modid examplemod with version 1.0.0. It picks the newest version, so with equal versions either copy can win. - Fabric Loader 0.20.1 also kept one and started. The mod list showed it once, with no warning.
In a dev run, a built jar of your own mod in run/mods is a second copy next to the code Gradle loads. NeoForge chose
the jar from run/mods, so changes in your code didn’t show in the game.
The loader stops only when it can’t treat the copies as one mod, such as two different jars that both contain the same
mod id. NeoForge then says Mod examplemod is present in multiple files, and Forge logs Found duplicate mods: with
the id and the files.
Checked on 19 November 2026 on NeoForge 1.21.1 and Fabric 1.21.1 servers. The NeoForge and Forge error lines are from their loaders’ own messages and weren’t reproduced.
Common causes
Section titled “Common causes”- Two versions of the same mod. An update was downloaded next to the old jar instead of replacing it.
- Your own mod twice, in a dev run. Running the game from Gradle already loads your mod from its source. A built
jar of the same mod copied into
run/modsis a second copy. - Two different mods that picked the same id. Rare, but it happens with short ids such as
coreorutils.
- Find the mod id, from the error message or from the mod whose changes don’t show.
- Open the mods folder (
run/modsfor a dev run) and look for every jar that contains it. The file names usually show it; if not, open each jar as a zip and checkfabric.mod.jsonorMETA-INF/neoforge.mods.toml. - Delete the older jar, or your own built jar in
run/mods. Keep one.
If it is your mod that clashes with someone else’s, change your mod id to something more specific. The id must be
lower case and is set in fabric.mod.json on Fabric, or in neoforge.mods.toml and the @Mod annotation on NeoForge
(NeoForge: mod files).
In Linen
Section titled “In Linen”Crash Doctor in Linen reads the crash report and the log next to it, then names the mod, the line and what to change. It’s free. Find out why a mod is not in the mod list covers the opposite problem.