MCDDD

Catches broken Minecraft packs before the game silently ignores them. Your pack is never uploaded: the checker runs inside your browser. Each check is listed in the log below.

Data packsResource packsMythic packsMinecraft 26.3What's new in 26.3 →Every code listed →

1 · Choose a pack

Drop your pack's .zip here or press Enter or tap to pick a file

A .zip data pack or resource pack, or a folder of Mythic configs zipped up. You can choose several at once and they are reported together.

    2 · How deeply to check

    The structural, layout, reference and lint checks always run. The deeper layers need Minecraft's own generated data, which is a few megabytes and is fetched once, then cached by your browser. Whatever you choose, the report states plainly which layers ran and which did not — a check that was skipped is never reported as a pass.

    Optional data to load

    3 · Check it

    Loading the checker…

    Checker fixes

    1. 2026-11-17, MCDDD 3.1.4 — A run failed due to an issue with checks MCD204 and MCD212. This was a defect on our side and has been corrected. Please re-run your pack to validate it again.
    2. 2026-11-16, MCDDD 3.1.4 — A run failed due to an issue with check MCD501. This was a defect on our side and has been corrected. Please re-run your pack to validate it again.
    3. 2026-11-16, MCDDD 3.1.4 — A run failed due to an issue with checks MCD601, MCD602, MCD603, MCD608 and MCD205. This was a defect on our side and has been corrected. Please re-run your pack to validate it again.
    4. 2026-11-16, MCDDD 3.1.4 — A run failed due to an issue with check MCD405. This was a defect on our side and has been corrected. Please re-run your pack to validate it again.
    5. 2026-11-16, MCDDD 3.1.4 — A run failed due to an issue with check MCD104. This was a defect on our side and has been corrected. Please re-run your pack to validate it again.
    6. 2026-11-16, MCDDD 3.1.4 — A run failed due to an issue with check MCD303. This was a defect on our side and has been corrected. Please re-run your pack to validate it again.
    7. 2026-11-16, MCDDD 3.1.4 — A run failed due to an issue with check MCD206. This was a defect on our side and has been corrected. Please re-run your pack to validate it again.
    8. 2026-11-16, MCDDD 3.1.4 — A run failed due to an issue with checks MCD508 and MCD509. This was a defect on our side and has been corrected. Please re-run your pack to validate it again.
    9. 2026-11-16, MCDDD 3.1.4 — A run failed due to an issue with checks MCD401 and MCD413. This was a defect on our side and has been corrected. Please re-run your pack to validate it again.
    10. 2026-11-16, MCDDD 3.1.4 — A run failed due to an issue with check MCD201. This was a defect on our side and has been corrected. Please re-run your pack to validate it again.
    11. 2026-11-16, MCDDD 3.1.4 — A run failed due to an issue with reading structure files (.nbt). This was a defect on our side and has been corrected. Please re-run your pack to validate it again.
    Run these checks from an AI assistantClaude, ChatGPT and Gemini can use MCDDD too. Step-by-step setup →

    Same checks, on the command line

    This page and the command-line tool run the identical checking core, so they cannot disagree. For CI, use the command line: it exits non-zero on findings and can write machine-readable JSON. Download mcddd.zip (no unzipping, no dependencies) and run it with Python 3:

    PYTHONPATH=mcddd.zip python -m mcddd check ./my_pack
    PYTHONPATH=mcddd.zip python -m mcddd check ./my_pack --format json --require-complete

    On Windows, in Command Prompt run set PYTHONPATH=mcddd.zip first; in PowerShell run $env:PYTHONPATH="mcddd.zip". Then python -m mcddd check my_pack.

    MCDDD · runs on Pyodide