Minecraft Mods Guide: Loaders, Modpacks, Crashes

The install order never changes, whatever pack you are building: pick a loader, install it for one exact Minecraft version, drop .jar files into the mods folder, and keep every mod matched to both the game and the loader. That last part is where things break. Below: how Fabric, NeoForge, Forge and Quilt differ, where the mods folder physically lives, what to read in the log after a crash, and which set is worth running on a weak machine. The one decision to make before downloading anything is the loader.

Short answer

• A mod built for one loader will not run on another. Write the mod list first, then choose.
• Mods are tied to a game version. When Minecraft updates, the whole set updates with it.
• Mods folder: %APPDATA%\.minecraft\mods on Windows, ~/Library/Application Support/minecraft/mods on macOS, ~/.minecraft/mods on Linux.
• Fabric setups almost always need Fabric API as a separate file in the same folder.
• The crash reason lives at the end of .minecraft/logs/latest.log.
• Weak PC starter set: Sodium, Lithium, FerriteCore, Entity Culling. Shaders are not part of it.

What a mod loader is, and which one to pick

A loader sits between the game's code and the mod's: it gives developers an API and tooling and keeps several mods running in one session without stepping on each other. Java Edition has four in circulation — Forge, NeoForge, Fabric and Quilt.

The consequence that matters is incompatibility. Different loaders expose different APIs, so a mod written for one is not going to work on another. Dropping Forge jars into a Fabric instance does nothing useful: the game either ignores them or falls over.

Which means you are not really choosing a loader, you are choosing mods. Write the list of what you actually want, then see which loader covers it. The split is easy to see in practice: Create publishes for Forge and NeoForge only, while Sodium ships for Fabric, NeoForge and Quilt.

Worth keeping in mind: Mojang does not officially support this kind of modding. It is community work, and nothing guarantees it survives the next update.

The mods folder, and matching versions

Files go into the mods subfolder of the game directory, which lives in a different place on each system:

The mods folder may not exist yet — it shows up after the first launch with a loader installed, or you make it by hand. Do not unpack anything: the .jar goes in as a file.

Then comes the version arithmetic that breaks more setups than everything else combined. Three things have to line up: the Minecraft version, the loader build for that version, and every single mod. When the game updates, the mods update too — a jar compiled for last release simply is not built for the new one.

There is a fourth number, and it is not a mod at all. The Mojang manifest pairs release 26.2 with Java 25; running on an older Java looks exactly like "the game will not start" and has nothing to do with your mod list.

Fabric adds a fifth item: Fabric API. It is a library of shared hooks and intercompatibility measures that most Fabric mods build on, and by downloads on Modrinth it outranks any individual mod. It installs like everything else — one file into mods.

Modpacks: when a launcher beats manual installs

Manual installation is fine at five mods and irritating at twenty. The problem is not difficulty; it is that Mojang's launcher keeps one shared game folder, so two setups on two different versions end up sharing a mods directory.

Third-party launchers solve exactly that. Prism Launcher, the Modrinth App and the CurseForge App — all of which the Fabric wiki carries install instructions for — give every instance its own folder, mod list, game version, loader and memory allocation. A broken instance can be deleted without touching the others.

Ready-made modpacks install from the same places in one click, and that is the safest way in: the set has already been assembled so the versions agree.

Why does Minecraft crash after installing mods?

Because of one of three things, nearly every time: wrong game version, wrong loader, missing dependency.

The evidence is in .minecraft/logs/latest.log, with compressed logs of earlier sessions sitting beside it in the same logs folder, named by date. Read the end of the file — the exception line usually names both the offending mod and what it was looking for.

A triage order that saves an evening:

Pull every mod and launch. If the bare loader starts, the problem is the set, not the installation. Put half back. Then binary search: half of the half, until one file is left holding the blame. Check each file's version. Not "for 26", but for your exact release. Check dependencies. Modrinth lists them explicitly — Iris, for example, is published as depending on Sodium.

What to run on a weak PC

The set is well known, free, and all on Modrinth: Sodium replaces the rendering engine, Lithium optimises game logic, FerriteCore and ModernFix cut memory use, Entity Culling stops drawing what you cannot see, and Sodium Extra puts back the toggles Sodium deliberately omits, like fog and particles.

A scale check, since anyone can call a mod recommended: Sodium is past 221 million downloads on Modrinth, FerriteCore past 147 million, Lithium past 124 million. The whole Modrinth mod catalogue held roughly 74,800 projects in September 2026, so this is the top of it rather than a personal shortlist.

Shader packs are not on the list — they spend performance rather than making it. If you want the picture anyway, the trade-offs are in the shaders on a low-end PC guide, and the settings and memory side is in FPS on a low-end PC. Shader packs are loaded by Iris, which Modrinth lists as depending on Sodium: they work as a pair, not as alternatives.

What usually goes wrong

• The game launches as if no mods exist. Almost always the vanilla profile is selected. Installing Fabric or NeoForge adds a separate profile line in the launcher, and it has to be picked by hand.
• One mod takes the whole set down. Loaders got mixed — a Forge jar sitting next to Fabric ones. Their APIs are different and there is no bridge between them.
• The pack broke after a Minecraft update. Working as designed: mods follow the game, and until the author ships a build for the new release, staying on the old version is the only option.
• A mod does not appear in game though the file is there. Check that it really is a .jar and not a renamed archive, and that it is in mods rather than loose in .minecraft.
• More allocated memory made things worse. Not a mod problem: the Java virtual machine does not go faster with a bigger heap, and the garbage collector has more ground to cover. The numbers are in the FPS guide.

Where to go next

An instance that starts reliably beats an instance with a hundred mods, and the cheapest way to keep it that way is incremental: add a few files, launch, play half an hour, repeat.

If crashes started before any mods were involved the cause is elsewhere, and general startup failures are covered in game crashes on startup, with frame drops in why FPS drops.

If you are modding a first playthrough, the walkthrough to the Ender Dragon and the beginner mistakes list still apply — mods change your tools, not the way lava works. Test what you remember with the Minecraft quiz, pick a handle with the name generator before joining a modded server, and warm up on the Kohi click test. Everything else for the game is on the Minecraft hub.

FAQ

Sources

• minecraft.wiki: Mod (loaders, incompatibility, Mojang's position)
• minecraft.wiki: .minecraft (paths per OS, logs folder)
• Mojang version manifest: current release and required Java
• Modrinth: Fabric API (hooks most Fabric mods rely on)
• Modrinth: Sodium (rendering engine replacement)
• Modrinth: Iris (shader loader, depends on Sodium)
• Modrinth: Lithium (game logic optimisation)
• Modrinth: Create (example of a Forge and NeoForge only mod)
• Fabric Wiki: installing the loader and mods, third-party launchers
• NeoForge documentation