Modpacks & mods

CurseForge and Modrinth in one catalog — search in one place, results ranked by relevance with infinite scroll. You don't have to care where something comes from. Every pack has a page of its own: a gallery, a version picker and the changelog of each version.

• One click from the card (hover ⤓ = the newest version) or from the detail, with navigation and live progress. Install asks which version, with the newest already selected.
• Transitive required dependencies are pulled in automatically.
• Search by project ID, slug (e.g. create-world-cz), title, or a whole CF URL. The default sort is most downloaded; going back from a detail returns you to where you were.
• Resource packs, shaders and data packs from CurseForge go to resourcepacks/, shaderpacks/ and datapacks/, not all into mods/.
• Click an author in the detail → their packs.
• An install can be cancelled at any point and leaves nothing behind.

When an author has disabled downloads outside CurseForge, the launcher never fetches that file itself. It opens the file's official CurseForge page in a window of its own (the window goes to CurseForge only), the page starts the download (or you press its Download button), and the launcher picks the file up from Downloads, checks its size and SHA-1 and puts it into the instance. We do not click for you and we do not work around anything. Progress shows N/M, you can skip, or cancel the install. If the window closes before the file arrives and the same file (same SHA-1) is on Modrinth, that one is used.

Got a pack from a backup or a friend? Import .mrpack (Modrinth) and CurseForge .zip — from the Import button, or by dragging it straight into the library. A pack whose overrides folder has a different name works, and in .mrpack client-overrides win.

An import needs a valid ZIP with modrinth.index.json or manifest.json. If an import fails, check that it is a complete pack and not just a jar.

On first start the launcher finds instances from Prism Launcher / MultiMC, the CurseForge app, the Modrinth app, ATLauncher, GDLauncher and the official launcher, and offers to bring them over. It shows the size first and leaves logs and caches behind. The same works any time from Library → From another launcher. It only reads the other launcher's data and changes or deletes nothing in it.

In the instance detail you manage mods: list, enable/disable, add, remove. Downloads stream with speed and ETA. A crash caused by a missing dependency or a duplicate mod is recognised and a fix is offered, see Troubleshooting.

Mod update checking is in the instance detail too — the launcher shows how many mods have a newer version, and you update one or all of them.

For an installed pack, a newer version is shown on the card, on the detail and once before launch. An update works the same when you pick a version, press Update before playing, or use Play from the web. You can go forward or back; worlds are never touched. Since Launcher 0.10 the update is smart and keeps your edits.

What you changed stays. The launcher compares every file of the pack three ways: what the pack had last time, what you have, and what the new version brings.

• A config you never touched gets the new version. A config the pack did not change stays yours.
• Where you both changed the same thing, the launcher asks: Overwrite with new / Keep mine / Show the difference, also "for all".
• Configs (toml, json, properties, options.txt, cfg, snbt) merge key by key: your keybinds and render distance stay and the pack's changes land. A setting that is new in the pack is taken without a question.

Your own mods, resource packs and shaders stay. Only what the pack itself brought and no longer ships is removed, and only a file exactly as the pack shipped it. A mod you updated yourself stays (unless the pack updated it too), and a mod you disabled stays disabled in its new version. Nothing already on disk is downloaded again.

A backup before updating. The launcher asks what to back up: mods and configs, worlds, screenshots (with sizes), and optionally Mod data (maps, Distant Horizons LODs, minimap waypoints, replays). Free space is checked first, progress shows and you can cancel. The last 5 backups are kept.

Going back is one click: instance detail → Backups. A restore lays everything out beside first and swaps afterwards, so if it fails (a full disk, say) the instance stays as it was. What mods wrote since the backup (minimap waypoints, map tiles) is not deleted. Links to folders elsewhere are not deleted on restore, and the backup shows how many it left out.

An update cut short (Cancel, a closed CurseForge window, a lost network) does not pass for finished. The instance stays on the old version, a second run fetches only the rest, and no mod is left in two versions. A file that failed to download keeps the mod's old version. Press Play and the launcher asks: Finish the update / Go back to the backup / Play anyway.

An update, a restore and a start of the same instance never overlap. For a pack that belongs to a server (the Play button), only its own instance is updated; instances you set up yourself are never changed.

• Mod-conflict detection and a lockfile (reproducible instance).
• Resource pack, shader and datapack managers — same experience as mods.