Launching the game

How the selected version and active modules/layers determine what mods actually load.

Selecting a version

Pick the Minecraft version to play from the version selector. Each version has its own independent set of modules — modules don't carry over between versions on their own (see Cloning modules for copying one across manually).

What actually gets included at launch

For each active module, Bricky resolves which mods to include based on that module's layer mode:

• Single — whichever one layer is currently selected for that module.
• Multi — every currently active layer, duplicate mods resolved automatically (see Modules & layers).
• Inherit — the currently active layer plus everything it inherits from layers below it.

Only modules you've toggled on are included at all — adding mods to a module doesn't do anything until that module is active.

If something feels wrong at launch

If the game launches with a mod missing or with one you didn't expect, check the module and layer state in the editor first — most of the time it traces back to which layer was actually active, not a launch-time bug. If the editor's own display (installed mod list, layer contents) doesn't match what actually loaded in-game, that mismatch itself is worth reporting.