[1.7.2] NBT and RAM Mem of ItemStack in MP.

[Ernio]

Hey,

 

Could someone say how correct is my thinking and answer later question:

 

In Multiplayer all NBT data for ItemStacks is saved on server side. Then the ItemStack (with its NBT) is sent to every player that will need to have it, and it will be saved to client's RAM.

 

Now let's say I have 3 string fields (i'll later convert them to integer Id's for .png) in NBT for every MyItem.class ItemStack that hold: "hand_txt", "body_txt" and "blade_txt".

 

Those strings are being read for all items that are instance of MyItem at least one time per tick (not sure) when custom renderer calls it.

public void renderItem(IItemRenderer.ItemRenderType type, ItemStack item, Object... data)

In this method renderer reads from NBT those 3 fields, pickups right icons and then renders them into one whole item.

 

The question is: Is reading from NBT on client side (since it is renderer) occurs "virtually" on client from itemstack's NBT saved inside RAM or for every tick, every player and every itemstack it is being resent from server and then read.

 

Someone told me that ItemStack NBT is sent to player once per his session, and ONLY updated when the server will detect any change it it's NBT - is this true? (because I really hope so).

 

We all know that reading from NBT (HDD) is something near dozens of thousands slower than RAM, and having it read every tick, for every player and loaded ItemStack will create a freaking LOT of requests to NBT.

 

Help Thanks.

 

 

[Ernio]

What about the second part:

 

"Someone told me that ItemStack NBT is sent to player once per his session, and ONLY updated when the server will detect any change it it's NBT - is this true? (because I really hope so)."

 

Everytime I make request for some NBT data I call something from data I've alredy got on my client's "virtuall" data or I redownload it from multiplayer server?

 

And ofc. thanks for response

 

Oh and why is this so important:

Let's say I have 100 players that stand in one place in which there are 1000 items (MyItem.class) on floor/in their hands. Since every itemstack's renderer calls for 3x NBT String fields ("hand_txt", "body_txt" and "blade_txt") on every tick that makes:

20(tick)*100*1000*StringSize (wchich is around 10-20bytes), and that can be equal up to dozens of MB. If that kind of data would be sent from server in one second it would cause total connection crash.

 

And yes - I am reading source myself (right now), just thought you might know some of this stuff alredy.