[1.19.2][Solved] Recipes that overwrite vanilla tools aren't loaded

[Boy132]

Hello!

 

I'm trying to overwrite the vanilla recipes for the wooden tools. I have this "wooden_sword.json" inside "resources/data/minecraft/recipes", for example. When checking ingame the recipe hasn't changed. (wooden sword is still crafted with wood instead of the new dirt)

I'm also overwriting the recipe for bread the exact same way (created a file "resources/data/minecraft/recipes/bread.json") and for bread it works.

I also tried it with the stone tools and it also didn't work.

 

No errors or hints in the logs. I'm using Forge 43.1.1. If you need more information let me know.

Thanks in advance.

Edited October 28, 2022 by Boy132

[warjort]

It's not a good idea to replace vanilla recipes or other vanilla datapack data by default in mods.

What do you think happens when 2 different mods try to do this.

 

Anyway, make sure you specify a dependecy on the forge mod in your mods.toml and that it says it should be loaded AFTER it.

That way your mod will be placed above forge in the datapacks when creating new worlds.

Quote

[[dependencies.${mod_name}]]
    modId="forge"
    mandatory=true
    ordering="AFTER"
    versionRange="[${forge_version},)"
 

Where obviously you need to replace the $x bits with the real values.

[Boy132]

9 minutes ago, warjort said:

Anyway, make sure you specify a dependecy on the forge mod in your mods.toml and that it says it should be loaded AFTER it.

That way your mod will be placed above forge in the datapacks when creating new worlds.

Where obviously you need to replace the $x bits with the real values.

Thank you! Changing the ordering did the trick.

  

9 minutes ago, warjort said:

It's not a good idea to replace vanilla recipes or other vanilla datapack data by default in mods.

What do you think happens when 2 different mods try to do this.

Don't worry. I'm going to use conditional recipes and config values later. The example above was basically just for testing.