Stable Creation Tools v1.9.1

Pack Merger

Intelligently merge multiple resource packs into one optimised pack.

Stable · Released and maintained — v1.9.1 for 1.21–1.21.11 and 26.x. Visual in-game merger with conflict scanner, per-asset resolution, and a /packmerge command suite.

What's new

Latest in Pack Merger

Full changelog
1.9.1 Latest 2026-07-20 Release

GUI & export refinements

  • Expanded version matrix to 1.21.11 and 26.x
  • Conflict scanner improvements
  • Headless /packmerge command suite

See it in action

Pack Merger v1.9.1 — the real thing, not a mockup

No demo video — run it yourself

We do not publish mockups as proof of working software. This page describes build 1.9.1: launch it, follow the tutorial step by step, or read the docs — every claim links to something you can execute today. Recorded walkthroughs are tracked on the roadmap.

Follow the tutorial instead

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

Pack Merger — feature registry

8 features across 5 categories — all real, all working.

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).

Quick start

Get started with Pack Merger in minutes

Follow these steps — most installs take under five minutes.

1

Step 1

Install the Pack Merger mod on the Minecraft version you target — keep the build matched to your version.

2

Step 2

Open Options → Resource Packs and press the Merge button to open the visual merger screen.

3

Step 3

Add resource packs in your preferred priority order — list order is the default priority per asset.

4

Step 4

Review the detected conflicts in the GUI: each colliding asset shows which packs provide it and the current resolution.

5

Step 5

Resolve conflicts per-asset (Keep / Lost / Use), bulk-resolve by category, or Resolve All by priority.

6

Step 6

Export the merged pack — one clean ZIP with the correct pack_format baked in; no ZIP tools needed.

7

Step 7

Apply the exported pack from the Resource Packs screen, enabled near the top of the list.

8

Step 8

For scripted or server-side merges, use the /packmerge command suite: scan, merge <a> <b>, export, import, list, conflicts, strategy, resolve and clear.

Full Pack Merger tutorial Documentation Download now

Compatibility

Versions & loaders

PropertyValue
Loader / platformFabric
Latest version1.9.1
Minecraft versions1.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

2026-07-20 Release Latest

GUI & export refinements

  • Expanded version matrix to 1.21.11 and 26.x
  • Conflict scanner improvements
  • Headless /packmerge command suite
Warning. 26.x builds are experimental
Fixed: exported packs could carry stale pack_format on some versions

Roadmap

Where it's going

Merge engine & GUI

done

Core merging with in-game GUI.

Smart conflict previews

next

Visual before/after previews of resolved conflicts.

Headless CLI

later

Server-side and scripted merging.

FAQ

Questions, answered

Does it modify my original packs?
No — originals are untouched; a new merged pack is exported, so you can re-merge any time.
Can I control conflict resolution?
Yes — per-asset Keep/Lost/Use choices, bulk resolution by category, and Resolve All by priority. Review detected conflicts in the GUI before export.
What versions are supported?
1.21 through 1.21.11, with experimental 26.x builds. Keep the mod build matched to your target Minecraft version.
Do I need ZIP tools?
No — merging and export happen entirely in-game, with the correct pack_format baked in.
Is there a headless option?
Yes — the /packmerge command suite supports import, list, conflicts, strategy, resolve, merge and clear for server-side and scripted use.
Can I undo an export?
Your source packs are never changed, so you can re-merge any time — just export a fresh merged pack.
How do I combine DPT colour themes?
Stacking resource packs directly causes conflicts — use Pack Merger to combine DPT packs (and any other packs) into one clean pack instead of fighting load order.
The exported pack looks wrong
Conflict resolution may have chosen a different source than you expected — reopen the merger and change the per-asset choice, or use Resolve All by priority. Exported pack_format staleness was fixed in 1.9.1.

Compatibility & limitations

What to know

Compatibility. 26.x builds use bundled mappings and are experimental.
Status. Released and maintained — v1.9.1 for 1.21–1.21.11 and 26.x. Visual in-game merger with conflict scanner, per-asset resolution, and a /packmerge command suite.

Downloads

Get Pack Merger

1.9.1 is the current release.

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.

And more · 26 products See the ecosystem roadmap

Pack Merger — ready when you are.

Install it, read the docs, and explore how it fits into the wider ecosystem.