Minecraft Datapack Structure Reference: Inspect Generated Files

Read the actual output before moving files

This reference describes the roles of the files emitted by Mine Mod AI. Exact paths and format numbers depend on the selected version. Use the generator's file inventory and pack.mcmeta rather than copying a layout from an unrelated release.

A datapack zip must expose pack.mcmeta at its root. If extraction adds a second enclosing folder, Minecraft may not see the pack. The data directory contains namespaces so one pack's resources can be identified independently of another pack's.

File roles

• ▸pack.mcmeta: the generated format declaration and pack description. Confirm the target game version before editing it.
• ▸data/<namespace>/function/*.mcfunction: ordered commands in newer layouts. Older targets can use functions; inspect your generated path.
• ▸data/minecraft/tags/function/load.json: references setup functions called when the pack loads or reloads.
• ▸data/minecraft/tags/function/tick.json: references recurring functions. Examine guards and work performed each tick.
• ▸data/<namespace>/loot_table/*.json: loot rules. An override under minecraft can replace vanilla behavior.
• ▸data/<namespace>/recipe/*.json: generated recipes and ingredient/result declarations.
• ▸README.txt: installation, generated names and start controls. It can explain a /function command that a generic installer cannot infer.

Resolve a function reference

For a generated id such as example:play, look for the namespace folder example and the function file play.mcfunction in that version's layout. Load/tick tags and calls inside functions must point to files that exist. Mine Mod AI's structural validator checks internal references for namespaces it owns.

Inspect the first function you plan to execute. A build function may place or replace blocks; quickstart may set teams or teleport players. Run these only in a copied test world until you understand the output.

Diagnose a loading problem

• ▸Confirm Java Edition; Bedrock manifests are a different format.
• ▸Confirm zip root structure and the declared target version.
• ▸Run /reload, read errors and check /datapack list enabled.
• ▸Check whether another pack overrides the same loot, recipe or namespace.
• ▸Confirm the documented start function and required permissions.
• ▸Keep logs and the exact generated files when reporting a failure.