What an instance holds
- Its own folder inside the launcher data folder.
- The game version and the loader: Vanilla, Fabric, Quilt, Forge or NeoForge.
- Mods, resource packs, shaders and data packs, settings and worlds.
- A log of every session — including the ones where the game never opened.
The instance screen
A summary at the top and tabs below: Mods, Modpack, Settings, Logs and Snapshots — on a server, also Console, Network, Players and Properties.
- Art, version, loader, state, play time and last session in a single panel, with install and launch progress over the art.
- Cover: an instance created from a modpack gets the pack logo; any instance accepts an image of yours.
- Memory with a default limit computed from the machine RAM. Any value can be set, and the launcher warns when it does not fit.
Snapshots and export
- Each instance can save the state of its mods, settings and loader — never the worlds — and go back to it later. The second snapshot costs only what changed.
- The launcher takes a snapshot by itself before every mod update and keeps the last five automatic ones. Restoring can be undone too.
- Export to
.mrpack(Modrinth) or.zip(CurseForge): the package points to the mods instead of redistributing them and says right away what was left out.
One copy of each mod
Downloaded mods, resource packs and shaders are stored once, and each instance gets a link to the file. Ten instances with the same Fabric API cost one jar on disk. A card in the settings shows what is stored, how much sharing saves, and cleans up what no instance uses anymore.