Pack registry

Register a pack.

Give the registry the URL of a packwiz pack.toml and it hands back a code like amber-otter-42. The registry stores the pointer, not the pack; your files stay on your host.

Look up a code

See what a code points at before adding it, or open the manage page for a pack you own.

Hosting a pack

Build it with packwiz. packwiz init, then packwiz modrinth add … or packwiz curseforge add …. Set version in pack.toml and bump it on each change; that is what Muster compares.
Serve the folder. GitHub Pages, a git-sync'd nginx, an object-storage bucket: anything that serves pack.toml, index.toml and the .pw.toml files over HTTPS.
Register here. The registry fetches pack.toml once to confirm it parses and to record the Minecraft and loader versions. Updates to the pack itself need no re-registration.

Server-only files (side = "server") are skipped on players' machines. CurseForge files whose authors forbid third-party downloads are listed for manual download rather than failing the sync.

What the fields do

Recommended memory: Becomes the default -Xmx, clamped to what the player's machine has. Players can override per pack.
JVM arguments: Applied while a player is "following the pack". Space-free flags only; the launcher cannot pass arguments containing spaces.
Server address: Purely informational: a chip on the pack card.
Pack id: Names the install folder. Keep it stable.

Rather host the list yourself?

Muster also reads a JSON pack list from a URL you control, with the same fields per entry. Players set the URL once in the Minecraft settings. Codes are simpler for most groups; the manifest suits communities with many packs.