Choose Java or Bedrock before choosing a mod.

Java Edition: build an isolated profile

1. Back up the entire world folder before changing its game version, loader, or mod set.
2. Choose one exact Minecraft version and one loader. Never mix Fabric, NeoForge, or Forge files in the same profile unless a project explicitly provides a compatibility layer.
3. Create a separate game directory for the profile. NeoForge's own guide recommends this isolation from the standard .minecraft directory.
4. Install the loader from its official site, launch the empty profile once, then close it.
5. Download mods from the author's primary page on a reputable catalog. Confirm edition, loader, Minecraft version, required API, dependencies, and whether the mod must also be installed on a server.
6. Place the mod JAR files in that profile's mods folder. Add a few at a time and launch between groups.
7. Keep the generated latest.log and crash report. They normally identify missing dependencies, wrong loader builds, mixin failures, or incompatible mods.

Fabric installation pattern

Fabric's official player guide says to select a mod built for Java Edition, the intended Minecraft version, and Fabric—not another loader. Many Fabric mods also require Fabric API. With the official launcher, install Fabric, select its profile, place compatible JAR files in that profile's mods folder, and launch. If the game fails, remove the newest addition and read the log before changing Java or the loader.

NeoForge installation pattern

Install the Java version required for your Minecraft branch, close the launcher, run the official NeoForge installer with Install client, then create a launcher installation using a separate game directory. Launch once so the mods folder is created. Add only NeoForge files for that exact Minecraft version. NeoForge explicitly recommends backing up the world before updating the loader or mods.

Bedrock Add-Ons: protect the world, then activate packs

Mojang distinguishes Java mods from Bedrock Add-Ons. For Bedrock, duplicate the world first. Open the world's edit screen, choose Resource Packs or Behavior Packs, and activate the Add-On under Available. For a new world, activate packs during world creation. Realms can distribute activated Add-Ons to connecting Bedrock devices. Mojang warns that combining many Add-Ons can reduce performance; test a small set and preserve an unmodified world copy.

Crash and update workflow

• Wrong-loader error: replace the file with the author's Fabric, NeoForge, or other correct build; renaming a JAR does not convert it.
• Missing dependency: install the exact required project and version, including dependencies of dependencies.
• World stops loading: do not keep saving attempts over the only copy. Restore the backup with the original version and mod set.
• Large modpack failure: preserve libraries and loader, then disable half the optional mods and repeat until the incompatible group is isolated.
• Server rejection: match the server's required client mod set and versions. Client-only visual mods and server-required gameplay mods are not interchangeable.