Prepare the destination first
Decide which instance receives the mod before downloading anything. An instance is a separate game setup with its own Minecraft version, loader, mods and settings. Give it a clear name such as “Survival test · Fabric” so you can distinguish it from a working setup.
Check that the instance starts on its own. Note its exact game and loader versions. For an existing world, make a backup while the game is closed; the backup guide explains what needs to be included.
Open the project in NimbusAtlas and select Choose a version. Match the release to that instance and read its dependencies. “Newest” and “correct for my setup” are different questions.
Install through Nimbus Launcher
- Open NimbusAtlas from Nimbus Launcher. This establishes the local connection used for installation. Opening the website directly in an unrelated browser session does not establish that connection.
- Choose a compatible file. Connected sessions offer Add to Nimbus Launcher for supported
.jarand.mrpackfiles. - Confirm in the launcher. The website sends the project and release identifiers to Nimbus on your own computer. Review the destination and the action in the launcher before confirming.
- Wait for the launcher result. The website's “Confirm in Nimbus Launcher” message means the handoff was accepted. It is not proof that all files have finished installing.
Install a mod manually
Install the correct loader using its own official instructions or your launcher's instance settings. Launch that empty instance once, close the game, then open that instance's game folder. Do not assume every launcher uses the default .minecraft folder.
Place the mod's .jar and its required compatible libraries into the instance's mods folder. Leave the JAR packaged; ordinary mod files are not installed by unpacking them or double-clicking them. When replacing a mod, move its old release out of the active folder so the loader does not see two copies.
The official Fabric instructions show the standard folder locations and profile selection. For a different loader, follow that loader's installation instructions; the folder name alone does not make a file compatible.
Modpacks and visual packs use different paths
A .mrpack represents a modpack installation and should be imported by a launcher that supports it. Putting it into mods does not install the pack. Modrinth explains supported installation routes in its modpack guide.
A resource pack usually goes through the game's resource-pack menu, while a shader pack goes through a compatible shader loader. Neither should be treated as an ordinary mod JAR. Follow the author's file instructions and the visual packs guide for those two cases.
Check that the installation did its job
Launch the destination instance and first use a disposable world. Open the mod's settings or deliberately use its main feature. A successful title screen is useful, but it does not exercise a new biome, recipe, multiplayer connection or rendering option.
If the game fails, keep the error and the most recent log. Undo only the change you just made, then launch again. If the original state works, you now have a much smaller problem to investigate. See the crash checklist before changing several unrelated settings.
Once it works, record the installed release and dependencies. Your next update is easier when you know exactly what the previous working state contained.
Sources & scope
Original NimbusAtlas workflow guidance. Official references support the technical details linked in the article. Check the selected release's own requirements when they differ. References reviewed October 8, 2026; no hardware benchmarks or hands-on testing are claimed.