Merge Minecraft Resource Packs Into One (26.3)

Written for Minecraft 26.3.

To merge Minecraft resource packs, copy each pack's assets folder into one new pack, then resolve every file both packs contain. A server can only offer one pack, so this is how you ship a model pack and a texture pack together.

Before you start

• Both packs unzipped into separate folders.

• A third, empty folder for the merged pack.

• A file-compare tool is useful. Any folder diff in your editor works.

• Read the pack basics guide if you have not built a pack before.

How the game loads several packs

The bottom pack in the selected list loads first. Each pack above it replaces or merges what it contains. So the pack highest in the list wins any conflict.

When you merge into a single file system, you decide what wins. You are doing by hand what load order does automatically.

Merge the packs

1. Copy pack A completely into the new folder, including pack.mcmeta and pack.png.

2. Copy pack B's assets folder over it. When your tool reports a conflict, do not overwrite blindly. List the conflicts first.

3. For each conflicting file, pick a winner or merge it using the table below.

4. Set the merged pack.mcmeta format range so it covers both packs' targets.

What to do with each type of file

• Textures and models. One copy wins. Keep the one from the pack you want on top. Item models in assets/<namespace>/items/<name>.json work the same way: one file per item, so one winner.

• Texture .mcmeta files. A higher pack with no .mcmeta gets default settings, not the file from a lower pack. Copy the .mcmeta along with its PNG.

• Language files. The game merges these across packs, and a missing key falls back to a lower pack. You can still combine them yourself: put both packs' keys into one assets/<namespace>/lang/en_us.json.

• sounds.json. An event's replace key controls whether your sounds replace the default ones (true) or are added to them (false, the default). Combine the event entries from both files into one file.

• Atlases. The game combines the sprite sources from all active packs for each atlas, so packs rarely conflict. In one merged pack, put all sources entries into one file such as assets/minecraft/atlases/blocks.json. See the atlases guide.

• font/default.json. The wiki does not describe how providers from different packs combine. Put every provider into a single providers list yourself and test it.

Merging a JSON file by hand

Take the top-level list from each file and join them. Here two lang files become one:

{
  "item.myserver.ruby_wand": "Ruby Wand",
  "block.myserver.marble": "Marble"
}

Keep exactly one set of braces, and no trailing comma after the last entry.

Keep namespaces unique

Most conflicts disappear if each pack uses its own namespace for new content, such as assets/models_pack/ and assets/textures_pack/. Only files in the minecraft namespace collide with vanilla and with each other. If both packs used assets/custom/, rename one folder and update every reference to it inside the JSON files.

Rename references, not just folders. A model that still points at the old namespace shows the purple and black missing texture.

Check it worked

1. Zip the merged folder and enable it alone in the pack list.

2. Look at one thing from each original pack. Both should render.

3. Open .minecraft/logs/latest.log and search for errors after pressing F3 + T.

Common problems

Half of my sounds are gone

A single invalid entry can make the game ignore the whole sounds.json. Check the commas where you joined the two files. The sounds guide has the format.

An item uses the wrong model

Both packs defined the same item file. Only one survives. Decide which and delete the other.

Animations stopped

The .png.mcmeta file was not copied with its texture.

The pack is marked incompatible

The merged pack.mcmeta has a format range that excludes 97. Fix the range.