minecraft-recipes-datagenlisted

# Minecraft Recipes and Data Generation ## Purpose Recipes, loot tables, tags and advancements are data pack JSON. Their schemas and even their directory names change between Minecraft versions, and a wrong file does not crash — it is silently ignored, so the recipe simply does not exist. Data generation solves this by making the game itself write the JSON from Java code that will not compile if the schema moved. This skill covers setting up datagen on each loader, writing providers, and the tag and serializer rules that hand-written JSON gets wrong. ## When to use - Adding a crafting, smelting, smithing or stonecutting recipe. - Adding a block drop, chest loot or mob drop. - Adding or consuming tags, especially cross-mod ingredient tags. - A recipe or loot table exists on disk and the game behaves as if it does not. - Setting up `runDatagen` / `runData` for the first time. - Writing a custom recipe type with its own serializer. - Bulk-generating block models, item models and blockstates for many blocks. ## When NOT to use - The loader, version and mappings are unresolved. Run `minecraft-project-conventions` first. - The content being generated for does not exist yet. Register the block or item first (`minecraft-blocks-items`), then generate its data. - Worldgen JSON — biomes, features, structures. Those are datapack *registries* with their own bootstrap mechanism; see `minecraft-worldgen`. - A pure data pack with no Java. Datagen needs a mod to run in. ## Requir