These builders target Minecraft’s 1.21+ data-driven JSON registries. Some schemas (mob variants, dialogs) are newer and still evolving — double check against the current version’s vanilla data before shipping.
Datapack Content Builders
Build JSON for custom enchantments, jukebox songs, paintings, armor trims, mob variants, dialogs, and banner patterns.
Quick guides
How to use this tool, and the questions players ask most.
Why is my 
datapack tick json not working?
Tick functions must be referenced inside data/minecraft/tags/function/tick.json with the format {"values": ["namespace:name"]}. If the path is misspelled or points to a missing .mcfunction file, Minecraft fails to execute it every 1 game tick.
Why is my Minecraft datapack not working?
Datapacks fail to load if the pack.mcmeta file has invalid syntax or an incompatible pack_format number. In Minecraft 1.21.4, the required pack_format value is 61, and you can inspect loading errors using the /reload command.
How do custom jukebox songs work in a datapack?
Custom jukebox songs require a JSON file placed in data/namespace/jukebox_song/ defining the sound event and comparator output. The comparator signal must be an integer between 1 and 15, and the file links directly to an existing sound event.
How do you add custom armor trims with datapacks?
Custom armor trims require JSON files in data/namespace/trim_pattern/ or data/namespace/trim_material/ in Minecraft 1.20 and newer. These files specify the template item, description translation key, and the asset_id that links to client resource pack textures.
Where are custom enchantment JSON files located in a datapack?
Custom enchantments are stored as JSON files in data/namespace/enchantment/ starting in Minecraft 1.21. These files define the max level up to 255, supported items, and effect components, which Datapack Content Builders can generate.
More on 9Minecraft
Other tools on 9Minecraft you may find useful.
More Data Packs tools
Other tools on 9Minecraft you may find useful.
