Jump to content

[1.16.4]Trying to remove vanilla recipe using Datapack fail


Recommended Posts

Instead of saying "it doesn't work", I say how it is. I fail at doing it. That's what I'm having:

  "type": "minecraft:crafting_shaped",
  "pattern": [
    " XX",
    " #X",
    " # "
  "key": {
    "#": {
      "tag": "forge:rods/wooden"
    "X": {
      "tag": "minecraft:planks"
  "result": {
    "item": "minecraft:wooden_axe"

It sits inside the data.minecraft.recipes folder. My goal is to entirely remove, or hide the vanilla recipe, so that it does not show up in Survival/Hardcore(Creative is fine). The problem is, trying to remove any of the structure expected by the engine will result in a "Couldn't parse data file minecraft:wooden_axe from minecraft:recipes/wooden_axe.json" error. This technically does what I want, hiding/removing the recipe. But certainly I do not want to do this while at the same time creating an error. 

In any of those threads users are talking about doing it, but actually never show "how" to do it. I've yet to figure if I can actually achieve it with Datapacks, or have to use the "normal" coding way due to the involvement of Forge, and how it overrides the vanilla datapack with its own.

Edit: So in this video the user is actually using  what I would call a "hack", by replacing the result with item minecraft:barrier. But I don't want to create a barrier, or Air, or whatever. I want to remove the recipe or hide it. Unless creating a replacer item is the only way to do it?


Edited by Cratthorax
Link to comment
Share on other sites

Sorry. I was busy this week. I watched a different tutorial, and found this hack quite convenient:

    "ingredients": [{ "item": "minecraft:air" }],
    "result": { "item": "minecraft:barrier" }

I had to change the achievement database accordingly for issues regarding barrier icon issues, in the crafting menu.

But to adress your proposal. The correct way to remove vanilla recipes is by adding a simple "false type" condition check?

Link to comment
Share on other sites

16 minutes ago, Cratthorax said:

But to adress your proposal. The correct way to remove vanilla recipes is by adding a simple "false type" condition check?

the condition would disable the recipe, so yes that's the "correct way"

Edited by Luis_ST
  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.