TileEntity loading

[Nauktis 2]

Hi,

 

I am having some issues with my design regarding the way TileEntities are created.

 

As you know, there are basically two ways for a TileEntity to be created.

- The Block creates it upon placement using createNewTileEntity(). There we have all the freedom to pass any information we want.

- The TileEntity is created (using default constructor) when loading a game that had one already there.

 

My problem is the following:

My TileEntity needs some configuration values when it is created (lets say the size of its inventory).

I previously stored this value in the NBT tag of the TileEntity and had no problem.

 

But this value is actually configuration and never changes, so I though it is a bit silly that each TileEntity saves it.

 

Before continuing I need to precise that I can not store that config value statically (MyModConfiguration.getConfigValue()) because my TileEntity is used by different blocks that each have a different config value.

Lets say I have block1 that has an inventory size of 10 and block2 that has an inventory size of 20.

 

The way to work around this is to ask the block of the TileEntity its config value (worldObj.getBlock(x,y,z).getConfigValue()).

My problem is that when a TileEntity is loaded the readFromNBT is called immediately before anything else from the TileEntity is set (world object, position, etc.)

My TileEntity is therefore trying to restore the inventory content while the inventory is not yet created because I can not access its size.

 

Would you see a way to work around this? How do you typically handle loading of TileEntities?

I hope my explanations are clear enough and thanks a lot beforehand.

[diesieben07 6693]

When creating your TE using createNewTileEntity give it the config value. Then in the TileEntity save it to NBT. I don't see the problem.

[Nauktis 2]

Alright, thought I would save some space if I managed to find the value without the need to save it in the NBT tag.

I'm probably over-engineering the stuff again -.-

 

Thanks for pointing it out

[diesieben07 6693]

You could just store the config value in the block class, assuming it doesn't change per block-type. Then get the block via getBlockType in the TE and get the config value that way.