[1.12] Is there a way to get the hardness of a block in a non-deprecated way?

[ctbe]

I do it like this and it works:

 

Blocks.BRICK_BLOCK.getBlockState().getBaseState().getBlockHardness(null, null);

 

Because Blocks.BRICK_BLOCK.getBlockHardness(...) was marked as deprecated.

 

Yet, I noticed that getBlockHardness(null, null) is not using the parameters for anything. It is simply calling another function that in the end, calls the deprecated getBlockHardness function and said function just returns the value of the variable blockHardness of the block in question. It does nothing with the parameters. To be more specific it calls the getBlockHardness of BlockStateContainer which in turn just calls the deprecated getBlockHardness of the Block class which in turn does nothing with the parameters it gets passed. That's why it works with null being passed as parameters.

 

I was thinking that maybe using getBlockState().getBaseState().withProperty(...) could help, but after a while looking through the code, I could find no such a property for hardness. It is all hardcoded in the block registering method registerBlocks() of the Block class.

 

Is there an alternative to using this method that all it does is simply call a deprecated method or is this the only way?

[Draco18s]

You should be getting the hardness from the IBlockState. If you don't have one, use Block#getDefaultState()

[ctbe]

Thanks. I changed it to use the IBlockState returned from the getDefaultState() method.

 

Though it still goes through the same path. It calls the deprecated method from the non deprecated one in the BlockStateContainer class. Unless I am missing something else.

 

After looking at the classes implementations it feels like there is no other way to achieve it since I see no other method that returns the value of the protected blockHardness other than the deprecated one which is used by the non-deprecated method.

[Draco18s]

Yes, but all of the IBlockState methods call the deprecated Block methods. But that doesn't mean you shouldn't be using them.

[ctbe]

Thanks for the clarification. I'll continue using that then.

[ctbe]

Got it. Thanks.

[jeffryfisher]

If you're dealing with a block type that has variants, then (in theory), each variant could have a different hardness. Therefore, if you want the hardness for a block in the world, you should use pos to fetch the block-state from the world (and if you want the hardness for a block that has already been broken from the world, then you need the prior blockstate from before it was broken).