Libraries & tooling

A developer's deep dive into the data-pack ecosystem: what each library and tool actually provides, how the Smithed / Weld / Lantern-Load stack lets packs coexist, and the full develop → package → distribute workflow.

Libraries

Drop-in, namespaced data packs that provide reusable functionality. Reach for a library instead of hand-rolling anything non-trivial (raycasting, GUIs, trig, player physics) — see the advanced techniques page for the patterns they replace.

The coexistence model

The Smithed ecosystem standardises how libraries live together. Each library is namespaced, versioned, and exposes its functionality through function tags rather than plain function paths. It receives inputs via scoreboard fake-players or storage NBT, and is merged with other packs by Weld using declarative merge rules. Version resolution is built on Lantern Load (#load:load). This "call the newest versioned function via a tag" convention is exactly what lets ten packs ship the same library without clobbering each other.

data/yourpack/function/load.mcfunction (guarding init behind a dependency)

# registered in #load:load; only init once the dependency is present
execute if score dep_pack load.status matches 1.. run function yourpack:init

Tooling

The editors, generators, mergers and dev mods that make authoring bearable. None are required to run a data pack — they exist to speed up writing, validating and debugging one.

Component builders — the things that write the JSON for you

A data pack is a pile of small JSON files, and most of them are faster to generate than to type. These build one component at a time and hand you the file; none of them need installing.

Validation and simulation

Two browser tools for the steps a generator does not cover: checking a pack you already have, and seeing what it will actually build.

Develop → package → distribute

Develop

Work directly in a test world's datapacks/<yourpack>/ folder (or symlink from a git repo), and keep a dedicated flat/creative world template for fast iteration. Edit in VS Code + Spyglass for validation and autocomplete; for large projects reach for a compiler (JMC/PackScript/Beet-Bolt). Iterate with the tight loop: save → /reload → /function yourpack:test. Bind /reload plus a test function to a repeating command block or a carrot_on_a_stick for one-key testing.

Debug

First, the failures that do not announce themselves

Most data pack bugs are loud: a command errors, a number is wrong. The expensive ones are silent, and nearly all of them have the same shape — a file that fails to parse is never registered. Nothing in the world tells you. The file simply does not exist as far as the game is concerned, so everything that references it quietly does nothing.

The first two are taken verbatim from production packs on 26.2; see the destination field and block particle options for the causes.

Read the log before you read your code

The game writes every load failure to its log — logs/latest.log in the game or server directory — at the moment the pack loads. Search it for your namespace right after a /reload. A parse error there names the exact file, which turns an hour of reading JSON into one line. If the log is silent and the behaviour is still wrong, the file loaded and the bug is in its logic, which is a different and much easier hunt.

The test loop

1. Save the file.
2. /reload — reloads data packs in place. It needs permission level 2. If a change still does not appear, rejoining the world is the fallback; some changes are only picked up on a fresh load.
3. /datapack list — confirm the pack is actually enabled. A pack that is present but disabled looks exactly like a pack with a bug. /datapack enable reports when a name is not a valid pack.
4. Check the log for your namespace.
5. Run the thing: /function yourpack:test, place the structure with /place, or roll the table with /loot.

Bind /reload and your test function to a repeating command block or an item for a one-key loop.

Tools, and what each one can and cannot see

• Validators — MCDDD, Spyglass, Misode — read your files against a schema. They catch shape errors before the game does, and they are fast. But a validator reads files; it does not run the game. Production packs on this site have had files pass validation clean and still fail to load, so treat a clean validator result as necessary, not sufficient. The load in latest.log is the verdict.
• Simulation — MCJIG shows what a jigsaw pool builds without generating a world.
• Step debuggers — the Datapack Debugger (#breakpoint, /breakpoint step|move|get) or mcfunction-debugger (DAP breakpoints, @s score inspection) for logic that loads but misbehaves.
• Profiling and live state — Datamancer, which also auto-reloads on file change.
• State you can print — tellraw or the action bar, and /data get storage yourpack:… to read storage.
• Version drift — the release journal shows, build by build, which registries changed and whether the data pack format moved. Check it before blaming your code for something an update removed.

Package

Get the structure right: pack.mcmeta with the correct pack_format for your target version, data/<ns>/function/…, tags in data/<ns>/tags/…, and data/minecraft/tags/function/{load,tick}.json (or Lantern Load's #load:load). Ship a resource pack alongside when you need custom models/textures/sounds — custom items use the item_model/custom_model_data components on 1.21.4+ (or CustomModelData earlier). Combine the RP + DP so custom items actually look right; Modrinth and Smithed can bundle both. Use Weld to pre-merge library dependencies into a single distributable pack when needed.

Distribute

Whichever platform you pick, tag supported Minecraft versions accurately, include install instructions, and ship an uninstall function so players can cleanly remove your pack.

Sources

• Smithed documentation · libraries
• Weld
• Lantern Load
• Bookshelf documentation · GitHub
• Iris · AjjGUI · TagLib · player_motion · BlockState · moxlib
• Misode · mcmeta
• Datapack Debugger · Datamancer · mcfunction-debugger
• Animated Java · BDEngine · Spyglass
• minecraft.wiki — Data pack format