MC 1.14.4 Getting certain values from existing blocks

[winnetrie]

I'm updating my mod to 1.14.4 (coming from 1.12.2) and a lot have changed.

Some of my blocks are relying on some "properties" from other blocks. For example resistance, hardness, mapcolor.

Are there any getters for those, or how would i retrieve those values?

An example for that is i have , in addition to the vanilla bricks, added 16 more (colored) bricks. They all need to have the same properties except the mapcolor as the vanilla bricks.

I can ofcourse add those properties at instantiation, but since they all are "the same" i want it to be inside the class. This way it saves me alot of work.

I have done this for 1.12.2. Now it doesn't work like that. So i wonder if there are other ways now.

[Animefan8888]

11 hours ago, winnetrie said:

I can ofcourse add those properties at instantiation, but since they all are "the same" i want it to be inside the class.

Create class.
public SomeBlock(Properties properties) {

  super(properties.hardnessAndResistance(hardness, resistance));

}

[winnetrie]

22 hours ago, Animefan8888 said:

Create class.
public SomeBlock(Properties properties) {

  super(properties.hardnessAndResistance(hardness, resistance));

}

Oh so i set them all in the super? I really like this "properties" thing

EDIT: How do i now "get" the hardness and resistance from an other block?

Edited August 8, 2019 by winnetrie

[Draco18s]

2 hours ago, winnetrie said:

I really like this "properties" thing

I don't. While that particular mod never got a 1.12 update (and a 1.14 update is as unlikely) the fact that those fields are locked down pretty hard is annoying for those of us who actually want shovels to freaking matter.

2 hours ago, winnetrie said:

How do i now "get" the hardness and resistance from an other block?

Blocks.IRON_ORE.getDefaultState().getBlockHardness(null, null)

As dirty as it seems passing null there, virtually no blocks should rely on it. No vanilla ones do.

[Animefan8888]

20 minutes ago, Draco18s said:

While that particular mod never got a 1.12 update (and a 1.14 update is as unlikely) the fact that those fields are locked down pretty hard is annoying for those of us who actually want shovels to freaking matter.

Why not just use a constant? They can't change anymore. Now you have to override their registry.

[Draco18s]

23 minutes ago, Animefan8888 said:

Now you have to override their registry.

Because this is less mod compatible. Two mods overriding the same block, someone wins and someone loses.

Even if those two overrides are for completely unrelated things.

Edited August 9, 2019 by Draco18s

[Animefan8888]

11 minutes ago, Draco18s said:

Because this is less mod compatible. Two mods overriding the same block, someone wins and someone loses.

Even if those two overrides are for completely unrelated things.

This is true so best bet is to stay away from overrides and use events.

[winnetrie]

10 hours ago, Draco18s said:

I don't. While that particular mod never got a 1.12 update (and a 1.14 update is as unlikely) the fact that those fields are locked down pretty hard is annoying for those of us who actually want shovels to freaking matter.

Blocks.IRON_ORE.getDefaultState().getBlockHardness(null, null)

As dirty as it seems passing null there, virtually no blocks should rely on it. No vanilla ones do.

Ah, i didn't know i could parse in a null. I never understood why there isn't just a simple method for it. Just 1 without parameters. Like other getters.

However i can set those values manually and perhaps this is more common to do, but how unlikely it will be, in future updates it's always posseble those values changes.

In this case if the blockhardness of bricks ever changes , my bricks their hardness will Always be the same. It is also less typing. I could maybe just make a constant for the value, so if it ever changes i just have to change the constant's value