Data pack: pack.mcmeta
MCD001 pack.mcmeta is missing
MCD002 pack.mcmeta is not valid JSON
MCD003 pack.mcmeta has no 'pack' object
MCD004 pack_format is missing
MCD005 pack_format is not a valid format number
MCD006 pack_format is not a known Minecraft data pack_format
MCD007 pack_format does not match the target Minecraft version
MCD008 pack.description is missing
MCD009 pack.description has an invalid type
MCD010 supported_formats is not understood by this version
MCD011 min_format/max_format are ignored by this version
MCD012 min_format is greater than max_format
MCD013 declared format range does not contain the target version
MCD014 overlay entry is malformed
MCD015 overlay directory does not exist
MCD016 overlay directory name uses illegal characters
MCD017 overlays are not supported by this format
MCD018 pack.png is not a valid PNG
MCD019 pack_format disagrees with the version named in the description
The pack's description names one Minecraft version while pack_format declares a different one. The number is what actually decides how the pack loads, so a mismatch means the pack is being validated -- and loaded -- as a version its author did not intend. Frequently paired with MCD204: a pack described as "1.21.10" but declaring format 41 (1.20.5-1.20.6) usually still has plural folder names too.
MCD020 filter block is malformed
Data pack: JSON files
MCD101 file is not valid JSON
MCD102 JSON object has duplicate keys
MCD103 file starts with a UTF-8 BOM
MCD104 JSON root has the wrong type
MCD105 file is empty
MCD106 macOS files the pack does not need (__MACOSX/, ._*, .DS_Store)
MCD107 file is not valid UTF-8
MCD108 editor, version-control or OS files the pack does not need
Data pack: folders and names
MCD201 no files under data/
MCD202 data/ contains a file where a namespace directory was expected
MCD203 namespace name uses illegal characters
MCD204 registry folder uses the pre-1.21 plural name
Minecraft 1.21 (pack_format 48, snapshot 24w21a) renamed every registry folder from plural to singular:
functions/ -> function/ loot_tables/ -> loot_table/ advancements/ -> advancement/ predicates/ -> predicate/ recipes/ -> recipe/ item_modifiers/ -> item_modifier/ structures/ -> structure/ tags/functions/ -> tags/function/
There is no aliasing. A plural folder in a 1.21+ pack is simply ignored: the pack loads with no error and does nothing. This is the most common cause of "my datapack stopped working on 1.21".
Fix by renaming the folders, or ship the plural copy inside an overlay whose format range covers <= 1.20.6.
MCD205 registry folder uses the 1.21+ singular name on an older pack
MCD206 unknown registry folder
MCD207 resource path uses illegal characters
MCD208 file has an unexpected extension for its registry
MCD210 file sits directly in the namespace with no registry folder
MCD211 registry folder does not exist at this format
MCD212 tags/ subfolder uses the pre-1.21 plural name
MCD213 not a directory that a data pack recognises
MCD214 worldgen folder uses a name 26.3 renamed
26.3 renamed two worldgen registries, and a data pack folder follows its registry's name:
worldgen/configured_feature/ -> worldgen/feature/ worldgen/configured_carver/ -> worldgen/carver/ tags/worldgen/configured_feature/ -> tags/worldgen/feature/
Read off the shipped 26.3 registry dump, where the old names are gone, and vanilla's own 26.3 data tree, which ships only the new folders. A pack targeting 26.3 that keeps the old folder is where a 1.21 pack that kept functions/ was: every file is fine, and the folder is most likely not read.
A WARNING, not MCD204's error, while the pack also declares a format below 121: there the old folder is right for those versions. An ERROR when nothing the pack declares is below 121: no version it supports reads the old folder, so what is in it cannot load.
To support 26.2 and 26.3 from one pack, keep the old folder in the base pack and add the new one in an overlay for format 121 and up. This check is silent when both exist, and feature references resolve against either name.
Data pack: references
MCD301 referenced function does not exist
MCD302 referenced function tag does not exist
MCD303 referenced loot table does not exist
MCD304 referenced predicate does not exist
MCD305 referenced item modifier does not exist
MCD306 referenced advancement does not exist
MCD307 referenced recipe does not exist
MCD308 referenced structure does not exist
MCD309 tag entry does not exist
MCD310 tag references itself, directly or in a cycle
Declared, not reported by this version.
MCD311 function is never reached from a lifecycle tag or another function
Nothing in the pack reaches this function: it is not in any function tag, no other function calls it, and no JSON file names it. That is fine for a function you invoke by hand or from a command block. Otherwise it is dead code, or the tag meant to run it is missing or misspelled -- check data/minecraft/tags/function/tick.json and load.json, and note the folder is tags/function/ (not tags/functions/) from 1.21 on.
MCD312 advancement parent does not exist
Declared, not reported by this version.
MCD313 referenced dimension does not exist
MCD314 reference could not be verified (no vanilla registry loaded)
MCD315 lifecycle tag is outside the minecraft namespace
MCD316 referenced structure tag does not exist
MCD317 referenced biome tag does not exist
MCD318 referenced worldgen structure does not exist
MCD319 referenced template pool does not exist
A jigsaw structure names a start_pool that this pack does not contain.
This is the quietest way a custom structure fails. The pack installs, /reload is clean, and every static check passes -- because nothing is malformed. The game only resolves the pool when it decides to place the structure, so it throws during chunk generation, naming no file, and stays dormant until a player walks into a chunk that happened to select it. The report arrives as a world-corruption bug from someone standing in the wrong biome.
Note which registry each field means. A structure's start_pool and a pool's fallback name worldgen/template_pool; a pool element's location names the .nbt template in data/<ns>/structure/, which is a different registry that merely shares a word.
MCD320 referenced structure set does not exist
MCD321 referenced configured feature does not exist
MCD322 referenced placed feature does not exist
MCD323 referenced configured carver does not exist
MCD324 referenced processor list does not exist
MCD325 referenced biome does not exist
MCD326 exploration map destination is written as a tag with '#'
BEFORE 26.3, exploration_map's destination is a structure TAG id written BARE:
"destination": "ns:on_dungeon_maps" correct before 26.3 "destination": "#ns:on_dungeon_maps" breaks the pack before 26.3
The field already means a tag, so the # is not part of the id. With it the loot table fails to parse -- and a loot table that fails to parse is never registered, so every reference to that file dangles at once. A cartographer trade, a chest pool and an item table can empty together while the only symptom is a villager with no map to sell.
That blast radius is why this is its own code rather than a note on MCD316: the id may be perfectly correct and the pack still broken, and the file that causes it is not the file where you notice it.
This flips at 26.3 (from data format 111). There the # is REQUIRED and a bare id means one structure -- see MCD328. This code only fires below it.
MCD327 reference is built by a macro and could not be checked
MCD328 exploration map destination names a structure tag without '#' (26.3+)
FROM 26.3, exploration_map's destination changed meaning:
"destination": "#ns:on_dungeon_maps" the tag correct "destination": "ns:on_dungeon_maps" ONE structure finds nothing "destination": ["#ns:a", "ns:tower"] a list, also allowed
The bare form was REQUIRED before 26.3, so every pack correct for 26.2 carries it. Carried forward, it parses cleanly, logs nothing, and asks for a structure named after the tag -- which does not exist. The map points nowhere. That is worse than the 26.2 failure (MCD326), which at least broke loudly enough to find.
Reported only when the name is provably a tag and provably not a structure: from the pack's own files, or for minecraft: from vanilla's registry dump. A pack that names its structure and its tag identically resolves to the structure and is left alone -- it works, just not quite as intended.
Measured before 26.3 shipped: every destination in 26.3-pre-1 is prefixed, 28 of 28.
MCD329 exploration map has no destination, which 26.3 requires
From 26.3 exploration_map REQUIRES a destination.
Before 26.3 an omitted destination defaulted to buried treasure, so packs relying on that default are correct for 26.2. On 26.3 the loot table no longer parses, and a table that does not parse is never registered, so everything pointing at it dangles at once.
To keep the old behaviour:
"destination": "#minecraft:on_treasure_maps"
MCD330 a jigsaw block names a template pool that does not exist
MCD331 structure templates that nothing in the pack references
Data pack: functions
MCD401 unknown command
MCD402 unbalanced brackets or quotes
MCD403 line has trailing whitespace
MCD404 macro line used but this format has no macros
MCD405 macro placeholder is malformed
MCD406 function contains a macro line but is called without arguments
Declared, not reported by this version.
MCD407 line uses a leading slash
MCD408 selector syntax is malformed
Declared, not reported by this version.
MCD409 command was removed or renamed in this version
MCD410 raw NBT used where item components are required
Declared, not reported by this version.
MCD411 file is not valid UTF-8
MCD412 line exceeds the command length limit
MCD413 execute chain ends without a run
MCD414 empty function body
MCD415 windows line endings mixed with unix
MCD416 tp @s does not move the command context
MCD417 line continuation runs past the end of the file
Data pack: command grammar
MCD501 command does not parse against the vanilla command tree
MCD502 unexpected trailing text after a complete command
Declared, not reported by this version.
MCD503 command is incomplete
MCD504 argument value is invalid for its parser
Declared, not reported by this version.
MCD505 command not verified (parser unsupported by this tool)
MCD506 selector is too broad for this argument
MCD507 resource id in a command argument does not exist
The command parses. Its grammar is perfect. The id it names simply does not exist, so the game rejects the line when it RUNS rather than when the pack loads -- no red text at /reload, nothing in the log until something triggers it.
setblock ~ ~ ~ minecraft:chain <- not a block in 26.2
That one is real: chain was split into iron_chain and the copper variants, so a pack carried forward from an earlier version keeps a setblock that does nothing. 49 of them in one generated file, all silent.
Three things are deliberately NOT judged, each giving up coverage to avoid inventing findings:
- ids outside
minecraft:-- may belong to a mod or a companion pack - ids the pack itself supplies under data/minecraft/ -- legal for registries like damage_type and enchantment
#tags-- a tag is not an entry in the registry the slot points at
And two gaps remain, reported as nothing at all rather than as passes: 76 minecraft:resource_location argument nodes (playsound among them) carry no registry in Mojang's tree, so their ids cannot be typed without guessing; and block STATE properties -- [facing=north] -- need the generated block report, which this bundle does not carry.
MCD508 particle is missing an option it requires
MCD509 entity equipment NBT that 1.21.5 removed (ignored on this target)
MCD510 block_state map uses the key another version needs
Data pack: JSON contents (schema)
MCD601 value has the wrong type
MCD602 required field is missing
MCD603 unknown field
MCD604 value is not one of the allowed values
MCD605 number is outside the allowed range
MCD606 unknown type id for this registry
MCD607 array has the wrong number of elements
MCD608 field does not exist at this version
MCD609 field is deprecated
MCD610 schema could not be fully resolved
MCD611 id is empty where the game looks it up
Data pack: packtest
MCD701 unknown test directive
MCD702 test directive has an invalid value
MCD703 test can never fail
MCD704 referenced test template does not exist
MCD705 test-only command used outside a test function
Data pack: structure files
MCD801 jigsaw block has no block entity
MCD802 structure file is not readable NBT
MCD803 structure file could not be read
Data pack: the run itself
MCD901 no command spec loaded; command-tree checks were skipped
Command-grammar validation needs Mojang's generated command tree, which cannot be synthesised. Build a bundle:
python -m mcddd fetch --mc 26.2 --server-jar path/to/server.jar
Every other check -- metadata, JSON, layout, references, lint -- runs without it. Only MCD5xx is skipped.
MCD903 spec version does not match the target version
MCD904 file could not be read
MCD905 no mcdoc schemas loaded; JSON content checks were skipped
MCD906 files past the Windows path-length limit (read anyway)
Resource pack: pack.mcmeta
MCD1001 pack.mcmeta is missing
MCD1002 pack.mcmeta is not valid JSON
MCD1003 pack.mcmeta has no 'pack' object
MCD1004 pack_format is missing
MCD1005 pack_format is not a valid format number
MCD1006 pack_format is not a known Minecraft resource pack_format
MCD1007 pack_format does not match the target Minecraft version
MCD1008 pack.description is missing
MCD1009 pack.description has an invalid type
MCD1010 supported_formats is not understood by this version
MCD1011 min_format/max_format are ignored by this version
MCD1012 min_format is greater than max_format
MCD1013 declared format range does not contain the target version
MCD1014 overlay entry is malformed
MCD1015 overlay directory does not exist
MCD1016 overlay directory name uses illegal characters
MCD1017 overlays are not supported by this format
MCD1018 pack.png is missing or is not a valid PNG
MCD1019 pack_format is a DATA pack format, not a resource pack format
Data packs and resource packs both declare a key called pack_format, and the number means something different in each. For Minecraft 26.2:
data pack "pack_format": 107.1 resource pack "pack_format": 88
Copying the number across from a working data pack produces a file that is valid JSON, a pack Minecraft still lists, and a "made for a different version" prompt with nothing to say which number is wrong.
The two number spaces have diverged since 1.13 and will keep diverging. Run python -m mcddd versions for both tables side by side.
MCD1020 filter block is malformed
MCD1021 language declaration is malformed
Resource pack: folders and names
MCD1101 no files under assets/
MCD1102 assets/ contains a file where a namespace directory was expected
MCD1103 namespace name uses illegal characters
MCD1104 unknown asset folder
MCD1105 asset folder does not exist at this format
MCD1106 asset path uses illegal characters
Resource locations are lowercase: a-z 0-9 . _ - and /.
A file named MyOre.png resolves perfectly on Windows and macOS, whose file systems ignore case, and is simply absent on Linux and for any lookup the game does case-sensitively. The pack builds, ships, and is broken for people who are not the author -- which is why it usually survives all the way to release.
Rename the file and every reference to it. On Windows, git may need git mv --force MyOre.png myore.png to record a case-only rename.
MCD1107 file has an unexpected extension for its folder
MCD1108 asset folder is empty
MCD1109 file sits directly in the namespace with no asset folder
MCD1110 not a directory that a resource pack recognises
MCD1111 asset folder uses a singular name; resource folders stay plural
Resource pack folders are plural and always have been: models/, textures/, blockstates/, particles/, sounds/.
The singular rename at format 48 (1.21) was data packs only -- functions/ to function/, loot_tables/ to loot_table/. Applying that habit to a resource pack gives you a model/ or texture/ directory the game does not read. Nothing loads from it and nothing is logged.
MCD1112 data pack folder found under assets/
MCD1113 editor or file-manager junk is packaged in the pack
MCD1114 sounds.json is in the wrong place
MCD1115 pack contains both data/ and assets/
Resource pack: models and blockstates
MCD1201 model parent does not exist
MCD1202 model parent chain is circular
MCD1203 model references a texture that does not exist
MCD1205 blockstate references a model that does not exist
MCD1206 blockstate has neither variants nor multipart
MCD1207 blockstate has both variants and multipart
MCD1208 model element coordinates are outside the allowed range
MCD1209 model has neither a parent nor elements
MCD1210 model face references an undefined texture variable
MCD1211 model overrides are ignored at this format
MCD1212 unknown display position
MCD1213 model file is its own parent
MCD1214 multipart condition is malformed
Resource pack: textures
MCD1301 file is not a valid PNG
MCD1302 texture .mcmeta is not valid for a texture
MCD1303 animated texture height is not a whole number of frames
MCD1304 animation frame index is out of range
MCD1305 .mcmeta has no texture beside it
MCD1306 texture is animated but has no .mcmeta
MCD1307 texture is not referenced by anything in the pack
MCD1308 texture dimensions are not a power of two
Resource pack: sounds
MCD1401 sounds.json is not valid for a sound index
MCD1402 sound event references an .ogg that does not exist
MCD1403 sound file is not referenced by sounds.json
MCD1404 sound entry type is invalid
MCD1405 sound event references another event that does not exist
MCD1406 sound volume or pitch is out of range
MCD1407 sound file is not Ogg Vorbis
MCD1408 namespace has sound files but no sounds.json
Resource pack: languages and fonts
MCD1501 language file is not a flat object of string values
MCD1502 language file name is not a valid locale
MCD1503 translation format placeholders disagree with en_us
MCD1504 font provider type is unknown
MCD1505 font provider references a file that does not exist
MCD1506 bitmap font rows are inconsistent
MCD1507 font provider is malformed
Resource pack: items and the rest
MCD1601 item definition has no model
MCD1602 item definition model type is unknown
MCD1603 item definition references a model that does not exist
Since 1.21.4 an item names a tree of item-model nodes, not a single model: range_dispatch on damage, condition branches, composite layers, each with its own fallback, ending in leaves that name a real model file.
This code means one of those leaves points at a model that is not in the pack or in vanilla. The game does not log it. It silently takes whatever fallback sits above the broken leaf, or renders nothing at all -- so the item looks fine until the exact condition that reaches the broken branch comes up.
Counting item definitions will not find this, and neither will counting models. Only following every branch to its leaf does.
MCD1604 atlas source type is unknown
MCD1605 atlas source references a texture that does not exist
MCD1606 equipment layer references a texture that does not exist
MCD1607 particle definition references a texture that does not exist
MCD1608 post-effect references a shader program that does not exist
MCD1609 waypoint style references a sprite that does not exist
MCD1610 item definition is malformed
MCD1611 dispatch node has no fallback
MCD1612 item definition spans more than one texture atlas
Resource pack: the run itself
MCD1901 no vanilla asset index loaded; cross-pack references unchecked
Resource-pack reference checks need to know what the vanilla game already provides, otherwise every "parent": "minecraft:block/cube_all" looks like a missing file. Build the index:
python -m mcddd fetch --assets --mc 26.2 python -m mcddd fetch --assets --mc 26.2 --client-jar path/to/26.2.jar
Without it, references into namespaces this pack does not own are left unchecked rather than guessed at -- so a clean report is not proof that the minecraft namespace references resolve. Everything the pack owns is still checked in full.
Mythic pack: config files
MCD2001 Mythic config is not valid YAML
MCD2002 Mythic config uses YAML this tool does not model
MCD2003 skill line is read by YAML as a mapping, not a skill
A skill line written without quotes, containing a colon followed by a space, is not a string to YAML. It is a mapping.
- say Boss: Attack! -> {"say Boss": "Attack!"}
Mythic asks YAML for a list of strings and is handed a Map, so the line never becomes a skill. Nothing is logged, because nothing is malformed: the file loads, the mob loads, and one line quietly does not exist.
It gets worse if the value starts with a colour code. YAML reads a leading & as an anchor, so - say &6Gruk&7: &4FALL BACK! loses the &4FALL outright -- the text that survives is not even what was written.
Quote the whole line:
- 'say Boss: Attack!'
effect:sound{s=ns:my.event} is fine and always was. YAML only breaks the line at a colon followed by whitespace.
MCD2004 skill line has trailing text Mythic will not read
Mythic pack: names against the plugin jars
MCD2101 unknown Mythic mechanic
The name is not among the mechanics declared by the plugin jars that were extracted. MythicMobs marks every mechanic with a @MythicMechanic annotation carrying its canonical name and aliases, and those annotations survive into the compiled class file -- so the jar is an exact, versioned registry, the same way Mojang's own registry dump is for vanilla.
This is a warning, never an error, and that is deliberate. The registry is only as complete as the jars supplied. MythicCrucible, MythicDungeons and ModelEngine each add mechanics; a Crucible pack checked against a MythicMobs-only registry would otherwise light up with false errors on correct configs. Extract every jar the server actually runs:
python -m mcddd mythic-fetch --jar MythicMobs.jar --jar MythicCrucible.jar
An unknown mechanic that really is a typo fails silently at runtime, which is why it is worth surfacing even as a warning.
MCD2102 unknown Mythic condition
MCD2103 unknown Mythic targeter
MCD2104 unknown Mythic AI goal or target selector
Mythic pack: cross-file references
MCD2201 skill is cast but never defined
MCD2202 model reference names a blueprint the pack does not ship
A model{mid=X} (or bodyclamp, modelpart, ...) names a ModelEngine blueprint that is not among the .bbmodel files shipped beside the config.
Each file is individually valid. The MythicMobs config is correct YAML naming a correct-looking model; the ModelEngine folder is a correct set of blueprints. Only the pair is wrong, and no single-plugin validator looks at both -- which is exactly why this is worth checking, and the same reason a data pack item component pointing at a model no resource pack ships is worth checking.
At runtime the mob spawns with no model at all: a plain vanilla entity. That reads as "ModelEngine failed to load" far more often than it reads as "the name is misspelled", so it tends to be debugged in the wrong place.
MCD2203 animation is not in the blueprint that plays it
A state{s=A} names an animation that is not in the blueprint the mob wears. Animation names are stored in the .bbmodel file itself, so the legal set is known exactly.
The mechanic succeeds. The model simply does not move. Nothing is logged and nothing looks broken until someone watches the mob and notices it slides into melee range without an attack animation.
Most state{...} lines name no model -- the blueprint comes from whichever mob cast the skill. MCDDD propagates blueprints from mobs through skill{s=...} to resolve them. Where two mobs with different models can reach the same metaskill, nothing is reported: either blueprint could be the right one, and guessing would invent findings.