First look at block hardness & blast resistance autogen

[ipad54]

This PR implements block hardness & blast resistance autogeneration from BedrockData block properties table to make sure the values are always up to date because of Mojang frequent changes.

Changes

Added build\generate-block-break-info.php tool which produces BlockHardnessValues and BlockBlastResistanceValues classes in \pocketmine\data\bedrock\block.

VanillaBlocks now always refers to hardness & blast resistance constant values in these classes when registering a block. However, if a block is indestructible in the game, I don't use the hardness value and only the blast resistance one. I did this because some obvious indestructible blocks (like water and lava) have positive hardness which can be exploited by hackers to destroy them in survival.

Tests

This has been briefly tested in the game. I didn't notice any behaviour changes with block breaking and explosions.

[dktapps]

Good work on this so far.

I didn't realize how much this was going to suck for shared properties though. Since we have constants for every block, we're not able to share break infos between different blocks. That's made me hesitate with this.

[ipad54]

Yes, but we don't actually know about Mojang plans, maybe they will add its own hardness to every block in the same group. Moreover, I've found some TODOs about this. The only thing I didn't solve yet is wood type hardness registration. It seems like we will have to return something like WoodLikeBlockIdHelper but with hardness & blast resistance, but for now all wood blocks use oak values until we discuss what to do about this.

[dktapps]

It seems like we will have to return something like WoodLikeBlockIdHelper but with hardness & blast resistance, but for now all wood blocks use oak values until we discuss what to do about this.

I really don't want to go down that road. I'm starting to see why you wanted to unit-test this instead of doing it this way.

[ShockedPlot7560]

Good work
I hope for your mind that you've managed to find an easy way to replace the VanillaBlock :/
It's sad for wood, but adding another class with mapping doesn't seem like a very good solution, especially if we want to withdraw from this type of class.
Having one constant per block doesn't shock me that much. It allows more flexibility if mojang decides to change the hardness separately for groups of blocks, as ipad says.

[ShockedPlot7560]

The ambition behind one constant per block seems OK to me. The question of wood seems to me to be one to be asked when Mojang has decided to separate the game, for later.

[dktapps]

I thought this was a good idea originally, but after seeing the changes it requires I think it's a bad idea to go forward. I think we'd be better with a unit test to not have to add a bunch of noise to the code or use the constants in weird ways.