Jump to content

[1.8] Dumbest revelation ever. ItemStack's damage.


Ernio

Recommended Posts

I started coding something a while ago and totally forgot that - while Blocks have metadata that holds 16 states, item's metadata is actually whole damn Integer.

 

I am currently saving few values (short and booleans) that can be packed into one int.

 

I've never in my life used itemDamage (metadata) outside "the current durability of tool idea", question is - is it safe to use itemDamage for something that is not the durability (like, totally)?

 

Up to this point I don't really see anything that might cause errors later, but just asking. :D

 

Yes/No will suffice.

1.7.10 is no longer supported by forge, you are on your own.

Link to comment
Share on other sites

Yup, thanks.

 

int itemDamage;
...
public NBTTagCompound writeToNBT(NBTTagCompound nbt)
{
     ...
     nbt.setShort("Damage", (short)this.itemDamage);
     ...
}

 

And this is why I have trust issues with Vanilla ;_;

1.7.10 is no longer supported by forge, you are on your own.

Link to comment
Share on other sites

A short still gives you a max value in the neighborhood of 32000, which should be enough for anyone.

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.


×
×
  • Create New...

Important Information

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