Talk:Data Pack

Datapack structure
Ok the structure is rather confusing for those attempting to get a datapack working. Sigh; i spent a while trying to add in new recipes.

the structure is the following with the name of the datapack needs to be done twice

datapack/namespace/data/namespace/recipes/test.json

Having two folders with the name of the pack really threw me for a loop. Aditionaly its the first namespace where you need your pack.MCMETA file. I hope you guys can make some awesome stuffs and post if you find out more info. 70.100.112.81 22:42, 27 November 2017 (UTC)


 * To be clear, it's not that the namespace is to be listed twice. The first is the name of the datapack as a whole and can be anything (and AFAIK, is only referenced in the "DataPacks" tag in level.dat to determine enabled status). The second is the namespace for the files it contains to be referenced in-game (such as ). You can have multiple namespaces, such as using the "minecraft" namespace to overwrite default files:




 * (also, be sure to use the "Add topic" button to properly create a new discussion section) Skylinerw (talk) 23:47, 27 November 2017 (UTC)

pack.mcmeta
As a modder and someone who have worked in deobfuscating Minecraft's binary, I realize that data packs and resource packs share the same "pack" section in the pack.mcmeta file, which are of the same properties and structure. Should we create a page dedicated to that? Liachmodded (talk) 13:40, 22 March 2019 (UTC)
 * No, resource packs have more properties (language for example) and a different pack format. They’re too different, to share data. FVbico (talk) 14:01, 22 March 2019 (UTC)
 * Turns out they are the same, as the vanilla resource and data packs do share the file in the client.jar. Feel free to grab and check! liach (talk) 05:18, 13 June 2019 (UTC)
 * They're not shared, as seen by the different description. FVbico (talk) 07:54, 13 June 2019 (UTC)