Overview #
Pack Merger combines multiple resource packs into a single optimised pack and resolves conflicts automatically. Instead of juggling load order and invisible clashes, you add packs in priority order, review exactly which pack wins per asset (Keep / Lost / Use choices, bulk resolution by category, Resolve All by priority), and export one clean, version-correct pack — with the correct pack_format baked in for your target Minecraft version (1.21 → 1.21.11 and 26.x). Your source packs are never modified. A /packmerge command suite supports headless, server-side and scripted merging for power users.
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.
Quick start #
- Install the Pack Merger mod on the Minecraft version you target — keep the build matched to your version.
- Open Options → Resource Packs and press the Merge button to open the visual merger screen.
- Add resource packs in your preferred priority order — list order is the default priority per asset.
- Review the detected conflicts in the GUI: each colliding asset shows which packs provide it and the current resolution.
- Resolve conflicts per-asset (Keep / Lost / Use), bulk-resolve by category, or Resolve All by priority.
- Export the merged pack — one clean ZIP with the correct pack_format baked in; no ZIP tools needed.
- Apply the exported pack from the Resource Packs screen, enabled near the top of the list.
- For scripted or server-side merges, use the /packmerge command suite: scan, merge <a> <b>, export, import, list, conflicts, strategy, resolve and clear.
Configuration #
Pack Merger tunes merge behaviour through the GUI and the /packmerge command suite. The automatic resolution strategy can be set explicitly, and per-asset choices override it everywhere.
| Setting | Default | Description |
|---|---|---|
| Merge strategy | By priority (list order) | /packmerge strategy sets the automatic resolution used by merge; list order is the default priority per asset. |
| Per-asset resolution | Keep / Lost / Use | Per-asset choices, bulk resolution by category, and Resolve All by priority in the GUI. |
| Target pack_format | Auto (1.21 → 1.21.11, 26.x) | Exports carry the correct pack_format for the target Minecraft version. |
| Source packs | Untouched | Originals are never modified — a new merged pack is exported; re-merge any time. |
Frequently asked questions #
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?
How do I combine DPT colour themes?
The exported pack looks wrong
Compatibility #
| Property | Value |
|---|---|
| Loader / platform | Fabric |
| 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 |
| Latest version | 1.9.1 |
26.x builds use bundled mappings and are experimental.