Jump to content

[1.12 -> 1.12.2 (latest)] NBT in json recipes being matched by


Recommended Posts

Posted (edited)

UPDATE: Ok, so I seem to have stumbled on something that was discussed to death by the devs back in Nov-2017. For reader reference see: https://github.com/MinecraftForge/MinecraftForge/issues/4516. I'll be investigating a custom recipe for my case, but am leaving this topic open for now in case there is a better solution someone can propose (I can't tell where the discussion ended up honestly...)

 

Hullo all,

Sometime between 1.12 and 1.12.2 (latest recommended build 2655), json shapeless ore recipes seem to have begun comparing NBT data. So what was a simple "item": "modid:itemname" for an ingredient regardless of nbt, seems to need something else now to mean "ignore nbt". However, I still only see the 1.12  "minecraft:item" and "minecraft:item_nbt" ingredient types which seems to indicate "minecraft:item" should match any nbt (and you use 'item_nbt' otherwise). Am I missing something for 1.12.2?


Here is a simple test recipe file 'i_shall_call_you_squishy.json'. Works for 1.12 & 1.12.1 recommended builds. Is broken for 1.12.2 though:

{
  "result": {
    "item": "minecraft:egg",
    "nbt": {
      "display": { "Name": "Squishy"}
    }
  },
  "type": "forge:ore_shapeless",
  "ingredients": [
    { "item": "minecraft:name_tag" },
    { "item": "minecraft:egg" }
  ]
}


Test cases:
1) an egg + default name tag --> OK for all versions!
2) an egg + name tag with custom name --> no recipe match in 1.12.2 but OK for 1.12 and 1.12.1
3) egg with custom name  + default name tag --> no recipe match in 1.12.2 but OK for 1.12 and 1.12.1

 

So for 1.12.2 how do I change "minecraft:name_tag" to mean "any name tag regardless of NBT data"?

i_shall_call_you_squishy.json

Edited by The_Wabbit
Updated info regarding Forge devs associated discussion

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.

Guest
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.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • When I first heard about Bitcoin back in 2018, I was skeptical. The idea of a decentralized, digital currency seemed too good to be true. But I was intrigued as I learned more about the technology behind it and its potential. I started small, investing just a few hundred dollars, dipping my toes into the cryptocurrency waters. At first, it was exhilarating to watch the value of my investment grow exponentially. I felt like I was part of the future, an early adopter of this revolutionary new asset. But that euphoria was short-lived. One day, I logged into my digital wallet only to find it empty - my Bitcoin had vanished without a trace. It turned out that the online exchange I had trusted had been hacked, and my funds were stolen. I was devastated, both financially and emotionally. All the potential I had seen in Bitcoin was tainted by the harsh reality that with decentralization came a lack of regulation and oversight. My hard-earned money was gone, lost to the ether of the digital world. This experience taught me a painful lesson about the price of trust in the uncharted territory of cryptocurrency. While the technology holds incredible promise, the risks can be catastrophic if you don't approach it with extreme caution. My Bitcoin investment gamble had failed, and I was left to pick up the pieces, wiser but poorer for having placed my faith in the wrong hands. My sincere appreciation goes to MUYERN TRUST HACKER. You are my hero in recovering my lost funds. Send a direct m a i l ( muyerntrusted ( @ ) mail-me ( . )c o m ) or message on whats app : + 1 ( 4-4-0 ) ( 3 -3 -5 ) ( 0-2-0-5 )
    • You could try posting a log (if there is no log at all, it may be the launcher you are using, the FAQ may have info on how to enable the log) as described in the FAQ, however this will probably need to be reported to/remedied by the mod author.
    • So me and a couple of friends are playing with a shitpost mod pack and one of the mods in the pack is corail tombstone and for some reason there is a problem with it, where on death to fire the player will get kicked out of the server and the tombstone will not spawn basically deleting an entire inventory, it doesn't matter what type of fire it is, whether it's from vanilla fire/lava, or from modded fire like ice&fire/lycanites and it's common enough to where everyone on the server has experienced at least once or twice and it doesn't give any crash log. a solution to this would be much appreciated thank you!
    • It is 1.12.2 - I have no idea if there is a 1.12 pack
  • Topics

  • Who's Online (See full list)

    • There are no registered users currently online
×
×
  • Create New...

Important Information

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