TileEntity vs. WorldSavedData

[Caffeinated Pinkie]

I need to store a single number with a specific Block type. The number should be modifiable by the user, which I already have a method for, and persist between games. Each Block in the world should have the number independent from the other ones. I should be able to easily retrieve the number frequently. Lastly, I need to be able to iterate over all instances of the Block in the world. That part doesn't need to be included with the numbers, but it would be convenient.

 

With that information, would it preferable to create an entire TileEntity for this Block type just for this single number, or would it be better to use the WorldSavedData system to store and retrieve it? I want to also consider compatibility with other mods that allow for copying of Blocks, like WorldEdit and MCEdit, as in the copied Blocks should have a number associated with them and should be part of the data structure that I can iterate over.

 

Thank you.

[TheGreyGhost]

That depends on what the valid range of numbers is.

If the numbers you are trying to store are heavily restricted (eg 100 different possible values) then use blockstates (more efficient).  You can cache the block instances in a custom data structure that you don't need to save (since you can easily regenerate it by iterating through all blocks when (eg) loading a chunk.)

 

Otherwise, use a TileEntity.  The list of all (loaded) tileentities is maintained by vanilla automatically, you just need to filter it.

 

7 hours ago, Caffeinated Pinkie said:

would it be better to use the WorldSavedData system to store and retrieve it?

Down that road lies nothing but pain and suffering....  Chunks loading in and out, other mods manipulating your blocks, multithreaded access, loss of synchronisation...

 

-TGG