DOCUMENTATION / INSIDE A SETUP

Mods, packs & resources

A pack's Minecraft and loader versions define what belongs in its game directory. Resource management does not remove provider permissions or compatibility limits.

Mods, core mods and Nilmods

The inherited Mods and legacy mod pages manage the selected setup's files. Core-mod and Nilmods help entries are retained for inherited engine paths; their presence is not acceptance of every legacy format in official-launcher preparation.

Use the exact loader/Minecraft versions required by a mod. Back up before changing a managed pack. Custom or disabled mods remain local during supported updates, so review their compatibility when the publisher's mod list changes. Catalog actions remain subject to source availability and authorization.

Resource packs and texture packs

Use the relevant page for the selected instance and a pack compatible with its Minecraft version. An inherited Texture Packs entry serves older game formats; it does not establish that any old runtime is supported by this alpha. Activate and verify the resource pack in Minecraft as required.

Shader packs

Shader packs need a compatible game version, rendering mod/loader and graphics setup. A download or file appearing in the shader page is not evidence that the renderer or pack will work on your device. Configure and verify it in the launched game.

Data packs

Data packs affect a world. Check the pack format and Minecraft version, and back up that world before adding, removing or upgrading one. Test changes on a disposable copy; a pack-file rollback cannot guarantee world compatibility.