How to Package and Share Your Json Things Content

Folder Layout

Json Things content ships as a datapack, a resource pack, or both depending on what you made. Items and blocks need textures and models, which live in a resource pack under assets/<namespace>/. Recipes, loot tables, and worldgen data live in a datapack under data/<namespace>/. The things folder itself is typically read from the datapack side, since it defines gameplay content rather than visuals.

A clean layout keeps both packs side by side with matching namespace names so IDs line up. Zip each pack separately, or combine them if your loader supports it, and drop them into the world's datapacks folder or the instance's resourcepacks folder.

Testing Before Sharing

Load your pack in a fresh world to catch missing references — a texture that exists in your dev world but wasn't included in the zip is the most common break. Verify every item, block, and recipe appears and functions. Check the log for warnings about unresolved IDs. Once everything works, share the zip; recipients just drop it in and reload. Because everything is data-driven, they can edit your JSON directly to tweak values without recompiling anything.