Just wondering if there is any detailed information/tutorials about the new BlockState added in 1.8?

 

I have managed to put together bits of information from various posts and the minecraft code and i think i have a basic understanding but i would really like all the information available before i start messing with it.

BlockState in the end is just a method to combine block and named metadata. Same as x,y,z coordinates are combined in BlockPos.

OTOH this is just a mess:

 

Blocks.planks.getDefaultState().withProperty(BlockPlanks.VARIANT, BlockPlanks.EnumType.JUNGLE);

 

We have to get the default state, then modify it, rather than having a way to access the state directly and involves a static property and an Enum.

 

I mean, fine, sure, BlockStates are nicer than metadata and can include world-based states (FenceGate:isInWall) but holy hells did the code get longer and harder to read. 

world.getBlockMetadata -> 3

means I need a hand dandy lookup table, yes, but it's a lot easier to remember that function call and a lot faster to type out.

Hi

 

You might find this link useful

http://greyminecraftcoder.blogspot.co.at/2014/12/blocks-18.html

 

-TGG

OTOH this is just a mess:

 

Blocks.planks.getDefaultState().withProperty(BlockPlanks.VARIANT, BlockPlanks.EnumType.JUNGLE);

 

We have to get the default state, then modify it, rather than having a way to access the state directly and involves a static property and an Enum.

 

I mean, fine, sure, BlockStates are nicer than metadata and can include world-based states (FenceGate:isInWall) but holy hells did the code get longer and harder to read. 

world.getBlockMetadata -> 3

means I need a hand dandy lookup table, yes, but it's a lot easier to remember that function call and a lot faster to type out.

 

Thats where i was a bit confused. Why make it so much more complex when metadata in a lot of cases was so much easier? I can see the potential benefit with the new system but a way to set metadata directly would have been nice.

 

Oh well thanks for the replies. 

Why make it so much more complex when metadata in a lot of cases was so much easier?

 

Probably a mid-point step towards the API.  I suspect there will be a revision farther down the line that will make it "simpler" again while retaining the benefits of the new system.

 

But...it probably means I'll be skipping 1.8

Probably a mid-point step towards the API.  I suspect there will be a revision farther down the line that will make it "simpler" again while retaining the benefits of the new system.

But...it probably means I'll be skipping 1.8

 

In that case that may be a possibility for me aswell... Im only about half way through the process of fixing all the errors in my classes, then i need to learn the new texture/model system and then finally i need to go through and fix everything that has been broken by the update... And on top of that i still have a ton of content i want to add to 1.7.10.

 

I know in the past there have been a lot of mc versions that most modders have completely skipped would you consider 1.8 to be one of those versions?

I know in the past there have been a lot of mc versions that most modders have completely skipped would you consider 1.8 to be one of those versions?

 

I think it will be more used than those skipped versions in the past, but yeah, there's going to be a A LOT of people--the lower skilled among us and those with less time--who will look at the sheer number of things that they'll have to relearn and say to themselves, "I think I'm happy with 1.7.10, I'll just add Gany's Surface for the 1.8 stuff."