Bedrock Addon Tools: Manifest, UUIDs & Pack Checker

Most Bedrock addons that "won't import" fail on the same few things, and none of them are in the addon's actual content. They are in manifest.json, the small file that tells Minecraft what a pack is. Two packs that share a UUID get treated as one pack, so only one installs. A version written as "1.0.0" instead of [1, 0, 0] is refused. A trailing comma breaks the whole file. And a .mcpack zipped from the folder instead of its contents hides the manifest one level down, where the game never looks.

These three tools cover that. The manifest maker writes a correct manifest for a behavior pack, resource pack, skin pack, or a behavior + resource pair that is already linked, with an optional Script API module. It can also hand you a starter .mcpack or .mcaddon that opens straight into Minecraft. The UUID maker gives you fresh IDs. The pack checker opens your file on your own device, explains each problem in plain words, and fixes the ones it safely can.

How to use

1. Pick a pack type in Manifest maker, type a name, and set the version and lowest game version.
2. For scripts, tick Add a script and pick the @minecraft/server version your game supports.
3. Tap Download starter .mcpack / .mcaddon, or copy the manifest.json into your own pack.
4. To check a pack, open Pack checker and drop your .mcpack, .mcaddon or .zip on it.
5. If items say "can fix", tap Fix and download and import the new -fixed file.