Debug a Minecraft Bedrock add-on

Validation catches most packaging and reference mistakes, so start there, then fall back to the runtime checklist for problems validation can't see. Keep going until validation reports zero errors, then tell the user what you changed.

1. Find the project folder

Validate the folder that contains behavior_packs/ and/or resource_packs/. A single pack folder (one with manifest.json) also works. If you can't tell which folder the user means, look for manifest.json files and ask if there's more than one candidate.

2. Run validation

Run the bundled summary script. Here and in later commands, <this-skill-folder> is the folder that contains this SKILL.md:

node "<this-skill-folder>/scripts/validate-summary.mjs" <project-folder>

It runs npx -y @minecraft/creator-tools@latest validate -i <folder> --json --force, sending the CLI's report files to a temporary folder. It then drops the dozens of "passed" entries, merges duplicates, checks that pack dependencies point at real packs (which the CLI doesn't), lists references to vanilla (minecraft:) content separately, and moves known false positives into a "likely noise" section. Exit code 0 means no errors; exit code 2 means validation couldn't run or found no project, so don't report success.

Why not call the CLI directly? You can (--json output has errors, warnings, recommendations totals and a projects[].items[] list), but three things trip people up: