Pack Merger
Intelligently merge multiple resource packs into one optimised pack.
Why it exists
Purpose
Running many resource packs means manual load order, visual conflicts, and wasted texture slots. Pack Merger combines packs into a single optimised pack while automatically resolving conflicts — so you get the best of every pack without the clashes.
Who it's for
Resource pack users, texture artists, content creators, and server owners curating a consistent look.
Key capabilities
Intelligent merge engine
BFS/diff-based conflict detection finds and classifies every collision.
Automatic conflict resolution
Deterministic resolution rules decide which pack wins per asset.
In-game GUI
A visual screen for selecting packs and reviewing merges before export.
Version-correct export
Exports with the correct pack_format for the target Minecraft version.
Features
Everything Pack Merger does
Merge Engine 2 features
Intelligent merging
Combines multiple resource packs into a single optimised pack — originals are never changed.
Automatic resolution
Deterministic rules decide which pack wins per asset during the merge.
Conflict Detection 2 features
Collision scanning
BFS/diff-based conflict detection finds and classifies every collision across packs.
Per-asset control
Keep/Lost/Use choices per asset, bulk resolution by category, and Resolve All by priority.
In-Game GUI 2 features
Visual merger screen
Add packs in priority order and review detected conflicts in the GUI before export.
No ZIP tools needed
Merging and export happen entirely in-game.
Command Suite 1 feature
/packmerge commands
Import, list, conflicts, strategy, resolve, merge and clear for server-side, headless use.
Version-Correct Export 1 feature
pack_format baked in
Exports with the correct pack_format for the target Minecraft version (1.21–1.21.11 and 26.x).
Getting Started
How to use Pack Merger
- Install the Pack Merger mod on the Minecraft version you target.
- Open the Pack Merger screen from the main menu.
- Add resource packs in your preferred priority order.
- Review the detected conflicts in the GUI.
- Export the merged pack and apply it from the Resource Packs screen.
Compatibility
Versions & loaders
| Property | Value |
|---|---|
| Loader / platform | Fabric |
| Latest version | 1.9.1 |
| Minecraft versions | 1.21, 1.21.1, 1.21.2, 1.21.3, 1.21.4, 1.21.5, 1.21.6, 1.21.7, 1.21.8, 1.21.9, 1.21.10, 1.21.11, 26.1, 26.1.1, 26.1.2, 26.2 |
26.x builds use bundled mappings and are experimental.
Version history
Changelog
1.9.1
GUI & export refinements
- Expanded version matrix to 1.21.11 and 26.x
- Conflict scanner improvements
- Headless /packmerge command suite
Roadmap
Where it's going
Merge engine & GUI
doneCore merging with in-game GUI.
Smart conflict previews
nextVisual before/after previews of resolved conflicts.
Headless CLI
laterServer-side and scripted merging.
FAQ
Questions, answered
Does it modify my original packs?
Can I control conflict resolution?
What versions are supported?
Do I need ZIP tools?
Is there a headless option?
Can I undo an export?
Compatibility & limitations
What to know
Downloads
Get Pack Merger
Ecosystem
Part of something bigger
Every Hero Studios product is engineered to work with the rest of the ecosystem — one design language, one performance bar, one long-term vision. Pack Merger belongs alongside these tools.
J2B MC
Recreate Minecraft Bedrock Edition inside your Java world — one button. All the mechanics, all the bugs, everything Bedrockified.
Stable v3.2.1 across 1.21–1.21.11. Recreate Minecraft Bedrock Edition into your Java world using a simple button — all mechanics, all the…
HeroSync
Latency compensation that makes high-ping gameplay feel local.
Released and maintained — r1.4.0 across 1.21–1.21.11 and 26.x. Built from 100 specification documents with a fully modular engine.
Default Yellow Theme
Default Yellow Themed in Minecraft!
Part of the DPT family of 10 colour themes — Default Yellow Theme (DYT). Java Edition only: 1.8.9 and 1.20.3–26.2.