Changes

No change in size ,  04:14, 27 July 2021
Copy Datapacks to MC1.16 archive
Line 8: Line 8:  
In your project, you have a folder “resources” that has to contain a folder “data”. This folder will be your datapack. Your mod can have multiple data domains, since you can add or modify already existing datapacks, like vanilla’s, Forge’s, or another mod’s.
 
In your project, you have a folder “resources” that has to contain a folder “data”. This folder will be your datapack. Your mod can have multiple data domains, since you can add or modify already existing datapacks, like vanilla’s, Forge’s, or another mod’s.
   −
Additional reading on resources can be found [[Resources|here/1.16]].
+
Additional reading on resources can be found [[Resources/1.16|here]].
    
== Overriding Files ==
 
== Overriding Files ==
 
To modify a datapack (be it the end-user or in dev), you need to know the mod ID and the registry name of the item/mob/advancement that you want to override. These can be found after launching the mod (F3+H), but providing it for users in a simpler way can be helpful (using GitHub will allow users to navigate the datapack you provide with the mod). You can then follow the steps found [https://minecraft.gamepedia.com/Data_Pack here] to create any datapack.
 
To modify a datapack (be it the end-user or in dev), you need to know the mod ID and the registry name of the item/mob/advancement that you want to override. These can be found after launching the mod (F3+H), but providing it for users in a simpler way can be helpful (using GitHub will allow users to navigate the datapack you provide with the mod). You can then follow the steps found [https://minecraft.gamepedia.com/Data_Pack here] to create any datapack.
372

edits