What's the best way to store block states? about blocks

[rvandoosselaer]

There is a dedicated thread for Blocks at the jMonkeyEngine forum. You can ask all your questions there.

I don't quite understand the question, but I'll try to answer it generally.

It's not a good idea to mix render data and business data together. In JME terms, it would be the same as storing game data on Spatials. If you want to add data to blocks, don't put this data in the Block class. Store the data and link it with the block id.

The Block class is pure data. It has an id, type, shape, ... It contains the bare minimum info so Blocks know how to render this specific block. A block will always render in exactly the same way. Some blocks however have only differences in shapes, or models as you call it.

A wedge block for example, actually has 4 different shapes. One shape facing north, east, south and west. Each shape is represented by a different block object (eg. oak_log-wedge_north, oak_log-wedge_east, ...). You could for example create an object (WedgeBlock), that holds a collection of blocks (Collection<Block> models) containing all the different shapes of a specific type. This way you have sort of a multi-model system.

For handling blocks, there is the Chunk class. A chunk is a way of organising and structuring block data. Internally it has optimizations for block data lookup etc.
A ChunkRepository is used to serialize and deserialize (save and load) block data using protocol buffers.

[Igrium]

That makes sense. Thanks!