Datapacks

A datapack changes data the game already reads: recipes, loot tables, advancements, predicates, tags and functions (.mcfunction). It works on vanilla servers and singleplayer worlds, with no plugins or mods.

#What to put in the request

• Minecraft version. It decides pack_format and the folder names (for example function/ in 1.21+, functions/ before).
• What it does: recipes (shaped/shapeless), loot changes, advancement trees, scoreboard mechanics, tick or load functions.
• Namespace, if you care what it's called.

A datapack for Minecraft 1.21.1, namespace "extras".
- Shaped recipe: 8 cobblestone around a coal block = 16 torches.
- Shapeless recipe: 4 rotten flesh = 1 leather.
- A load function that creates a "deaths" scoreboard and shows it in the sidebar.

#How Codexe verifies a datapack

Datapacks have nothing to compile, so Codexe loads the pack on a real vanilla Minecraft server in its build sandbox, offline, and reads the server's log for errors in recipes, functions, advancements or JSON. The server version is chosen from the pack's pack_format: the newest installed version the pack is written for.

Test servers cover 1.20.1, 1.20.4, 1.20.6, 1.21.1, 1.21.4, 1.21.5, 1.21.8, 1.21.10, 1.21.11, 26.1.2, 26.2 and 26.3. If the layout is wrong for the version (for example functions/ on 1.21), Codexe corrects the folder names.

A pack with errors is repaired like code. Ready means the pack loaded cleanly.

#Install

Download the ZIP, put it in world/datapacks/ (or the world's datapacks folder in singleplayer), then run /reload or restart. Check with /datapack list.

#Limits

Datapacks can't add genuinely new blocks or items with new behaviour, and they can only react to what vanilla exposes (advancements, predicates, scoreboards). For event-heavy logic, use Skript or a plugin.