Builder
"Builder" in the sidebar is where a modpack is put together as a project, without installing anything. Until the project becomes an instance, neither Minecraft nor the mods are installed: the project keeps the list of mods with pinned versions, resource packs, shaders and configs.
A finished project can be installed as an instance, exported to .stzhk, or tried with a test run.
New project
- Sidebar → "Builder" → "Create project"
- Name, Minecraft version and loader
- "Create"
A Modrinth modpack can become a project too: the "Import .mrpack" button.
Contents
The "Contents" tab is what goes into the modpack, in the sections "Mods", "Resource packs", "Shaders". For each mod:
- Enabled / disabled — a disabled mod stays in the project, lands disabled in an instance and is left out of the export
- Required / optional — a mark for whoever installs the modpack
- Side — "Client", "Server" or "Both"
At the top — search within the contents and the total size of the modpack.
Catalog
The "Catalog" tab searches Modrinth and CurseForge, already narrowed to the project's Minecraft version and loader. Required dependencies are added together with the mod, and a mod that won't sit next to those already added is not added — the launcher tells you what it conflicts with.
Compatibility
The check works without installing — from what mod versions declare on Modrinth and CurseForge, and from the description inside the .jar itself, which lists the versions of other mods it accepts.
- "Problems" — what is missing (a missing dependency can be added with one button) and what won't work together. Mods added as a file or without a version can't be checked — they are listed separately
- "Dependency graph" — how the project's mods are linked: what depends on what, what is incompatible with what
Configs
The "Configs" tab holds the mod settings files that travel with the modpack: into the export and into an instance. Edit them right in the launcher or with "Open in VS Code"; every file keeps a history of changes: you see what changed and can bring back the previous version.
Finished modpack
- "Test Run" — quickly creates an instance
[TEST] <name>with the project's mods and configs, to try the modpack in the game - Export → "Create instance" — the same, but under a name of your choice
- Export → "Export to .stzhk" — the modpack file. With "Embed mods in archive" the file is bigger, but installing it needs no internet; without it, mods are downloaded during the install
The modpack's name, version, author and description are in the "Settings" tab.
Build it together with friends
With experimental features on (Settings → General → "Experimental features"), a project gets a "Build together" button: friends see the project in "Friends" and edit it with you, and nobody has to install it. More — Co-op build.
What's next?
- Modpacks — installing, updating and formats
- Mod Collections — a set of mods that adapts to any version