I am just trying to wrap my head around the concept, and am trying to determine if I have the correct logic about meta data, specifically about the functions getMetaFromState and getStateFromMeta.
... am I the one who sets the metadata values in getMetaFromState, or do they exist elsewhere before I set them there.  And if I set them there, will that be what gets passed to getStateFromMeta?

 

Sorry if this is a dumb question.  I've been searching the forums and docs and have yet to make the logical leap.

And on a related note, is there a function I can call to get the current metadata for a block? (eg. the 4 bit integer)

Crash Course in block states:

 

You know how torches sit on different sides of a block?

You know how dispensers can face in different directions?

You know how there's grass and snowy grass?

You know how there's both sand and red sand?

You know how fences connect to each other in different directions?

 

All of those things are block states. States of the block that define some behavior, be it a different texture, model, or behavior.

 

Metadata is the underlying implementation of how blockstate information (which is complex) is saved to disk. Some states (like fence connectivity) is not saved as it is a property that can be determined by looking at the world.

 

1.13 The Flattening removed all "its actually a different block" states, so Red Sand is now its own block, rather than a "variant state" of Sand. Same goes for the 16 wool colors (and their associated dyes and the fact the dye and the wool metadatas were mirrors of each other for no god damn reason).

Thanks for this, but I understand what block states do.  I was just wondering if I was the one in control of the metadata (of my custom blocks) by using those two functions, or if the minecraft assigned their own metadata to my blocks when I set block states.

1 hour ago, jottinger said:

I was just wondering if I was the one in control of the metadata

Yes.

You rule.  Thanks.