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.
Build JSON for custom enchantments, jukebox songs, paintings, armor trims, mob variants, dialogs, and banner patterns.
← All 137 toolsThese 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.
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.
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.
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.
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.
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.
