Seeking useful documentation on ItemStack usage

[Cerezo]

Hello,

 

I'm new to the Forge modding community and I have been working on a small project for a couple days, and I have been able to troubleshoot every issue I had until now. Simply put, I need an item to use as a reusable crafting ingredient (see Botania's Mortar and Pestle). My original idea was for the item to have itself as containerItem, but as it turns out, that (obviously) isn't a possibility.

 

Looking for help on the internet, all similar threads I have found are, at least, dated 2017 and make use of the hasContainerItem() and getContainerItem() methods, which have since been deprecated. The comments on the Deprecated tag point me to an "ItemStack sensitive version", which I haven't been able to find. Also, the Forge docs don't mention ItemStack and, apart from this, I haven't been able to find any documentation on it.

 

I would be very thankful.If any of you could point me to either ItemStack documentation or the right methods to use for my problem.

 

Thanks in advance.

[Novârch]

  On 5/14/2020 at 5:19 PM, Cerezo said:

see Botania's Mortar and Pestle

Expand  

You know Botania's code is open source, right? If you don't here's it's GitHub page.

[imacatlolol]

Sadly, almost all of the documentation (even the JavaDocs in the code) is horribly outdated or lacking, as you mentioned.

For your case, the "ItemStack sensitive version" comment refers to the hasContainerItem and getContainerItem in IForgeItem, which Item implements. Basically, just add an ItemStack parameter to the deprecated versions and it will override the new versions.

[Vinyarion]

Are you saying you are returning the original ItemStack reference in the getContainerItem method? I'm pretty sure you have to return a new/copy ItemStack, not just the same reference

[Draco18s]

  On 5/14/2020 at 8:27 PM, Vinyarion said:

Are you saying you are returning the original ItemStack reference in the getContainerItem method? I'm pretty sure you have to return a new/copy ItemStack, not just the same reference

Expand  

Depends on what you're doing.

If you're using a tool as an "ingredient" and want to damage the tool, yes, you return the same stack that was passed in (after calling AttemptDamage on it).

[Cerezo]

  On 5/14/2020 at 8:27 PM, Vinyarion said:

returning the original ItemStack

Expand  

I'm saying I can't find any docs on ItemStack usage, so I'm not using it at all. imacatlol's comment helped. The tool will not recieve damage, by the way.

[Draco18s]

  On 5/14/2020 at 8:39 PM, Cerezo said:

I can't find any docs on ItemStack usage

Expand  

ItemStack is a vanilla class. It represents a (enchant-able, stack-able, damage-able) form of an Item (which is a prototypical singleton).