How to deal with items that can take more than 65536 damage

[[NoOneButNo]]

Explanation: Items that can take more than 65536 damage (let's say a custom shield with 240000 durability) will 'break' when reaching that damage. By break, it means that it will simply vanish without playing the item sound break or whatever. To replicate this 'issue', simple create an item (no need for a code because this basically works with items that can be damaged. This can be easily replicated. armor or shield would be the best as they can easily be damaged or use override the hitEntity of an ItemSword and damage it by more than 65536) that has a durability of more than 65536 damage and damage it until the damage of the item reaches 65536. After 'reaching' it, it will disappear like a thin air.

 

 

[jabelar]

Yes, that's supposed to happen. Any item stack that gets damage of that amount is considered empty.

 

The code for ItemStack.isEmpty() method is:

    public boolean isEmpty()
    {
        if (this == EMPTY)
        {
            return true;
        }
        else if (this.getItemRaw() != null && this.getItemRaw() != Item.getItemFromBlock(Blocks.AIR))
        {
            if (this.stackSize <= 0)
            {
                return true;
            }
            else
            {
                return this.itemDamage < -32768 || this.itemDamage > 65535;
            }
        }
        else
        {
            return true;
        }
    }

 

[MFMods]

my first instinct was to close the tab (gah, another guy wants to make overpowered gear), but on the second thought, the answer is applicable to many questions, so i'll get to typing...

 

yes, it can be done. no, you can't go above 64k, don't try to fight that limit directly. but sure, solutions exist - are we programmers or silverfish?

 

first of all, sometimes you don't need to reach the original goal, the "that-s-it" solution. in many cases the "that-s-mostly-it" solution is good enough. and it tends to take 4x-20x less time. let's define the task - let's say your task is " item with 240k durability". would it be ok for it to mostly act as if it had 240k durability? meaning, if you give it 60k durability and have it take damage 1/4 of the time, that's functionally similar to having 240k durability. and it takes minutes to implement.

 

another way (which would be suitable for more complicated variation of what you need), is to give your item 100 durability, keep the actual value elsewhere (in nbt for example or cache+worldsave), and keep the durability set to percentage of the current value compared to the maximum value. with this solution, the value does not necessarily need to be the durability. all that is left to do is make a handler for tooltip event and add one line that explains things.

[Draco18s]

You have to use NBT for numbers that large.