Resource pack merger for Minecraft

A server can send only one resource pack, and some players want one zip instead of five. Add your packs here and get one pack back. The work happens in your browser, the packs are not uploaded.

Name of the new pack

Add two or more packs. You can also drop the zips anywhere on the page.

Description

Which pack wins

The order of the list is the order in the game: the pack at the top wins. When two packs change the same texture, model or sound file, the file of the higher pack is used and the other one is listed under "taken from the higher pack", so you see what got lost. Move a pack up or down with the buttons.

Files that are joined, not replaced

Some files hold a list for the whole pack. If one pack simply replaced the other, half of your custom items or sounds would vanish. These are joined:

sounds.json: the sound events of all packs. The same event in two packs: the higher pack's.
lang/*.json: the texts of all packs.
font/*.json: the providers of all packs in one list. This is what keeps rank tags, emojis and custom GUIs of several plugins working together.
atlases/*.json: the sources of all packs.
models/item/*.json with overrides: the custom model data entries of all packs, sorted by number.
items/*.json (1.21.4 and newer) when both use custom model data with range_dispatch or select: the entries of all packs.
pack.mcmeta: from the top pack, with the overlays and languages of the others added.

Two packs that use the same custom model data number on the same item cannot both win. The merger keeps the higher pack's and tells you. That has to be fixed in the plugin's settings, by giving one of them another number. The same goes for two packs that use the same character in a font. The merger cannot see that one, so check your rank tags and menus in the game.

Questions

Packs for different versions? The new pack keeps the version of the top pack. The report tells you when the packs do not have the same format. A newer or older game shows a warning but usually still loads the pack.
My zip has a folder inside. That is fine here: a pack that sits one folder deep is read correctly, and the new zip has pack.mcmeta at the top, as the game needs it.
For a server: upload the new zip, then put its link and SHA-1 in server.properties. The SHA-1 is shown after the download. The resource pack check writes the lines for you.
What is not handled: password protected zips, zips over 4 GB, and shader or OptiFine files that need to be joined by hand (they are copied, the higher pack wins).

Something wrong or missing here? Tell me, requests decide what I add next. More tools: all tools.