1 · Choose a pack
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.
3 · Check it
Loading the checker…
Report
Passed — badge earned
Issued only for a pack with no errors, no warnings, and every checking
layer actually run. The certificate records a digest of the pack's
contents, so it can be verified later with
python -m mcddd verify.
This pack failed. Every failure is logged and audited against MCDDD's own code for accuracy. If the checker got it wrong, we fix the checker.
Last checked packs
None yet.
Checker fixes
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
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
