Cloning modules

How "Clone from another module" and "Clone from other version" are supposed to behave.

Bricky has two ways to copy mods from somewhere else into the module you're currently editing. Both open a picker, then a blocking "Cloning…" progress modal while the copy runs — the launcher is unusable until it finishes, on purpose, so nothing can be changed mid-copy.

Clone from another module (same version)

Copies mods directly between two modules on the same Minecraft version. Since both modules target the same version and loader, the mod files themselves are just copied as-is — no re-downloading.

Clone from other version

Copies a module's mods from a different Minecraft version into the one you're currently editing. This can't be a raw file copy, since the source version's exact jar may not even be compatible — instead, each mod is freshly re-resolved and downloaded for your current version and loader.

If a mod has no compatible build for the target version, it's skipped and listed as failed rather than aborting the whole clone. If something that did fail turns out to be a dependency of something that succeeded, you'll get a conflict prompt — same "remove it" / "remove it and its dependents" choice you get when deleting mods manually.

What happens to layers

Whichever source layers you select, cloning creates a brand-new layer in the target for each one — it never merges a source layer into whatever target layer you currently have open. This matters especially for Inherit-mode sources, where merging into an unrelated existing layer would corrupt the inheritance chain.

The source module's layer mode (Single / Multi / Inherit) is copied onto the target too, using the same safe mode-switch logic as manually toggling it — so an Inherit-mode clone actually ends up with working inheritance on the target side, not just a label that says so.

If the target module started out with nothing but an empty, unused layer (e.g. a fresh module's default empty layer), that empty layer is removed once the new cloned layers are in place, instead of being left behind as clutter you'd have to delete by hand.

Layer limits still apply

Same 5-layer cap as manual layer creation (or higher, if you've turned on Unlimited layers in Settings). If a clone would push a module past the limit, the remainder is merged into the last layer that could be created rather than failing outright.