I wrote a manifest.json parser that fills in your pack's compatibility info for you — where does it get it wrong?

One of the most tedious parts of publishing a Bedrock pack anywhere is retyping information that's already sitting inside the file. So on Bedrock Bazaar the upload unpacks your .mcaddon server-side and reads manifest.json instead of asking you.

What it pulls out right now:

• min_engine_version, turned into the minimum Bedrock version shown on the listing
• Required experimental toggles, so players know before they download
• Declared Script API modules and their versions (@minecraft/server and friends)
• Pack UUIDs, which then get matched against other listings so declared dependencies auto-link

It also guesses a category from what's actually in the pack rather than the name: a skin_pack manifest goes to Skin Packs, a behavior+resource pair goes to Add-Ons, a resource-only pack containing a ui/ folder goes to UI Packs, world_template goes to Worlds.

The guessing is the part I'm least confident about, and it's why I'm posting. Packs in the wild are messier than the docs suggest — multi-pack bundles, subpacks, weird folder layouts, manifests with modules the format didn't originally anticipate. I've tested against what I could get hold of, which isn't a lot.

If you make packs: what's in yours that you'd expect a parser to trip over? Happy to test against anything you're willing to point me at, and I'd rather find the gaps now than have it mislabel someone's upload later.

https://bedrockbazaar.com

Not affiliated with Mojang or Microsoft.