Install Pack Merger #
Install Fabric Loader for 1.21 (plus Fabric API if the downloads page asks for it), place the JAR in your mods folder, and launch with the Fabric profile.
- 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.
Working with Pack Merger #
Product-specific steps, separate from the general install guide above.
Merge from the GUI
Open the **Resource Packs** screen and press the **Merge** button to open the visual merger. Add packs in your preferred **priority order** — the list order decides which pack wins per asset by default. The engine scans for conflicts using **BFS/diff-based conflict detection**, finds and classifies every collision across packs, then exports one clean pack. Your **originals are never changed**.
What you'll see. The merger screen lists your selected packs in order, then a conflicts panel: each colliding asset shows which packs provide it and what the current resolution is.
Resolve conflicts
Per-asset choices are **Keep / Lost / Use** — keep a pack's version, drop the asset, or use a specific pack's copy. Bulk resolution works by category, and **Resolve All by priority** applies the list order everywhere at once. Review the detected conflicts in the GUI before exporting — you always know exactly which pack wins per asset.
Export a version-correct pack
Export produces a single ZIP with the correct **pack_format** baked in for your target Minecraft version (1.21 → 1.21.11 and 26.x). No ZIP tools needed — merging and export happen entirely in-game. Enable the exported pack from the Resource Packs screen like any other pack.
What you'll see. The exported pack appears in your resourcepacks folder with a generated name; enable it at the top of the Resource Packs list for highest priority.
Headless merging from chat (power users)
Server-side and scripted merging uses the /packmerge command suite:
- scan — detect conflicts across imported packs without merging.
- merge <a> <b> — combine two packs headlessly.
- export — write the merged pack with the target pack_format.
- strategy — set the automatic resolution strategy used by merge.
/packmerge scan
/packmerge merge <a> <b>
/packmerge export
/packmerge import | list | conflicts | strategy | resolve | clearCombine DPT colour themes
The DPT family ships as separate colour packs — stacking resource packs directly causes conflicts. Use **Pack Merger** to combine DPT colours (and any other packs) into one clean pack instead of fighting load order.
Tips
- Order packs before merging: list order is the default priority.
- Originals are never modified — re-merge any time.
- Ships 1.9.1 across 1.21 → 1.21.11 and 26.x.
Common problems
Exported pack shows the wrong pack_format
Textures look wrong after enabling the merged pack
26.x export warns
Folder locations by platform #
| Platform | mods / resourcepacks folder | config folder |
|---|---|---|
| Windows | %appdata%\.minecraft\mods · \resourcepacks | %appdata%\.minecraft\config |
| macOS | ~/Library/Application Support/minecraft/mods | ~/Library/Application Support/minecraft/config |
| Linux | ~/.minecraft/mods · ~/.minecraft/resourcepacks | ~/.minecraft/config |
MultiMC / Prism users: these folders live inside Instances/<instance>/.minecraft/. Match the build to your exact Minecraft version — the compatibility table in the docs lists every supported version.
Configure #
Settings live in the config folder (JSON5 files you can edit by hand) and, where available, in the in-game settings screen the mod adds. The exact keys and keybinds are listed in the documentation and the FAQ below.
Tips for Pack Merger #
- Keep Pack Merger on the version range shown on its product page.
- If it doesn't load, confirm the JAR is in the right mods folder for the launcher and version you chose.
- Bedrock Edition, mobile, and console can't run Java Edition mods or packs — for a port or custom variant, request a commission.