The useful answer first
Install the pack as its own instance through a compatible launcher. Do not merge it into another profile or replace pinned mods before the original pack launches.
A modpack is more than a list of mods
A pack manifest identifies Minecraft, a loader and particular project files. The instance can also include configuration, scripts, resource packs and overrides that make those files work together. Installing only the projects you recognise does not reproduce the tested pack.
Treat the manifest, overrides and pinned releases as one unit. The pack’s newest version can target a different Minecraft or loader version from an older release, so choose the pack release first and let that release define the instance.
Use a launcher that understands the pack format
Use whichever compatible launcher already fits your setup. It has to understand the pack format, fetch the allowed files and apply its overrides to a separate instance.
The button beside a release opens that exact file on CurseForge or Modrinth. We won’t dump you on the project homepage and make you find it again.
Install and test the client pack
- 01
Back up existing worlds and create a new instance rather than reusing a custom profile.
- 02
Choose the exact modpack release you intend to play.
- 03
Install it through a launcher that understands that pack format.
- 04
Wait for the manifest, overrides, loader and game assets to finish installing.
- 05
Launch once with no extra mods and create a temporary test world.
- 06
Check the pack’s own documentation for required Java or memory settings.
- 07
Only import a copied world after the unmodified pack starts and saves correctly.
Update the pack as a pack
A single-mod update can add a dependency, remove an integration or change network compatibility. If the pack builder has not tested that combination, the instance is now a custom fork even if its name still matches the original.
Clone the working instance before updating. Prefer a published pack update, read its notes and test a copy of the world. When moving between major pack versions, preserve both instances until the new one has loaded, saved and reconnected successfully.
The server needs its own pack preparation
Do not upload a client instance blindly. A published server pack can leave out client-only mods and include startup files or server configuration. NeoForge recommends a separate server-pack instance when one exists; otherwise, prepare a separate copy and remove a client-only file only when you know that is what it is.
The server and joining clients must still agree on the pack release, Minecraft version, loader and all network-relevant projects. Preserve the world, configuration and startup files together when migrating hosts.
When a pack fails to install or launch
- Confirm the launcher supports that exact pack format and release.
- Repair or recreate the instance before manually replacing manifest files.
- Check that the configured Java version matches the pack’s Minecraft and loader generation.
- Read the first loader or dependency error instead of responding only to the final crash line.
- Remove additions until the original pack launches, then test custom changes one at a time.
- Keep the last working instance and world backup until the replacement has survived a proper play test.
Straight from the source
Sources and further reading
We read the docs so you do not have to hunt for them mid-crash. For one mod, the file you picked still gets the final word.
Try it on a real mod
Pick a release and check it
Choose your game version and loader, then see whether the exact file fits your setup.