Loading...
Vanilla datapacks — recipes, loot, advancements and placeable builds, with no plugin on the server.
Describe what you want — a custom crafting recipe, a loot table, an advancement, or a whole structure — and the AI writes a vanilla-compatible datapack. No plugin and no special server software: a datapack runs on the plain Minecraft server everyone already has.
What comes out is a real pack rather than a sketch: a pack.mcmeta with the right pack_format for your version, namespaced data/<yourpack>/ folders, strict JSON with no comments and no trailing commas — a server refuses the file over either — and small .mcfunction files instead of one enormous one.
Mojang renamed the folders inside a datapack at 1.21: singular names (data/ns/recipe/, data/ns/loot_table/) from 1.21 onwards, plural ones (recipes/, loot_tables/) on 1.20.x and older. The generator writes whichever your version needs — but only if it knows which version that is.
A pack built for the wrong side of that line loads without an error and simply does nothing, which is the hardest kind of failure to spot. Say "for 1.21.4" in your description, and set the version in Project Settings → Build so every later message inherits it. The Minecraft Version picker there only appears once you switch off Use global build settings, which is on by default.
Ask for a house, a ship or an arena and you get a build function rather than a schematic: drop the pack in world/datapacks/, run /reload, then /function yourpack:build and the structure appears where you are standing.
It is ordinary setblock and fill logic, so you can open the file afterwards and move a wall by hand.
There is nothing to compile, so a datapack project is finished the moment the files are written.
To download it, press the Export button in the toolbar — datapack, config, Skript and README projects carry one where a plugin has Build. Ctrl + E does the same from the keyboard, and on a phone or a narrow window the ⋮ button in the toolbar carries it in its Export section, as Download source (.zip).
Unzip it into world/datapacks/ on your server, run /reload, and /datapack list should show it enabled.
If /reload reports nothing at all, the pack is usually one folder too deep — the path that has to exist is world/datapacks/yourpack/pack.mcmeta, not world/datapacks/yourpack/yourpack/pack.mcmeta.
8 of 22 in Minecraft Studio · Last checked 16 September 2026 · Previous: Script Editor