How to Metadata with Blocks / minecraft 1.9.4-1.12+

[leplopp]

Hello,

 

I have a problem with my mod IDs, my ID management is very wasteful and i will be fixed this with Metadata for Blocks. I have no idea how to do it.

My Mod have 1500 blocks with no metadata the Blocks are in a array, i want the IDs in the metadata because forge has a maximum ID limit.

If the mod included with other mods, minecraft crashed because there is a ID limit.

Can someone show me how to use Metadata in Minecraft 1.9.4 - 1.12+

 

An example would help very much.

 

Thanks in advance

 

[Draco18s]

Metadata in 1.9+ is blockstates.

Metadata is just the underlying integer representation.

 

http://mcforge.readthedocs.io/en/latest/blockstates/states/

 

You will want to combine blocks that have similar functionality (e.g. all colors of wool in Minecraft Vanilla are the same block, but with different metadata) but separated by some "TYPE" aspect (color, material, etc)

Edited August 1, 2017 by Draco18s

[leplopp]

ok thanks for your help

[jeffryfisher]

In case you haven't read it elsewhere: Because a Minecraft world has millions of blocks in play at any given time (view distance in blocks squared  x 256 height; do the math), block data is extremely limited. Instead of instantiating and saving an entire class object for each block in the world, there is only one instantiation of each class (what you'll see called a singleton around here). In effect, all block-class fields are static even if they're not declared as such.

 

What's stored (in chunks) in the world are arrays of short (16-bit) integers, one archaic short per block. Of each 16-bit short, 12 bits are used for block ID (0..4095) and 4 bits become "metadata" (0..15). Having coded satellite telemetry back in the stone-knives & bear-skins dark ages of the 1980s, I feel right at home. YMMV. This 16-bit system may change someday, maybe as soon as MC v1.13, but for now that's what we have.

 

Whenever a block class is put to work, it needs to be handed its context (its world and position therein). Vanilla coding already handles the translation from  metadata to properties and back again. I recommend stepping through those processes at least once to become familiar with what's being done for you (and wrap your head around the virtually static nature of block classes in everything except properties).

 

Note: If you design a block subclass to use a property for a non-display purpose (e.g. behavior), then you should research the code for telling the renderer to ignore your property.