[1.8] Add a variant. Example : add new type of wood

[Koward]

Hi !

 

I decided yesterday to learn the way Minecraft handles block variants. Wood, wool...

As an experiment, I decided to create a new type of Wood Plank, an "hard" wood. It would be harder and have a bricky-woody texture.

I wanted to create a custom state with the new ExtendedBlockState.createState() from net.minecraftforge.common.property.

But it seems that works to changes states or compare when the state already exists initially in the block, which is obviously not the case here.

So I decided to check the metadata.

But it wouldn't work because I can't access the META_LOOKUP array of EnumType.

So tried another approach. And I ended up with

Block HardWood = (new BlockPlanks()).setHardness(1.5F).setResistance(10.0F).setStepSound(Block.soundTypePiston).setUnlocalizedName("hardWood");
        GameRegistry.registerBlock(HardWood, "hard_wood");
        Minecraft.getMinecraft().getRenderItem().getItemModelMesher().register(Item.getItemFromBlock(HardWood), 6, new ModelResourceLocation("stratification:hard_wood", "inventory"));

 

But it doesn't work either. I'm sure there is something I miss here.

[diesieben07]

You just need to make your own Block like you would for any other block.

[Koward]

Really ? But that's stupid. What's the point of the whole BlockState concepts then if it's not to allow easy use of variants ?

And what will happen when I will uninstall the mod ? I was hoping this method would allow easy reverse into the DefaultState that is specified in the BlockPlanks class.

[diesieben07]

Really ? But that's stupid.

Why?

And what will happen when I will uninstall the mod ? I was hoping this method would allow easy reverse into the DefaultState that is specified in the BlockPlanks class.

The Block will disappear, just like any other modded Block.

[Koward]

The Block will disappear, just like any other modded Block.

 

Exactly. When possible, if possible, that should be avoided by replacing the block with a vanilla one.

You can't tell me there is no way to do that. It seems so logical.

[diesieben07]

Unfortunately there is no way to do that, except with a 2nd mod which must be installed when the world is loaded without the block-adding mod for the first time.

[Koward]

That's so disappointing. It should be made. The amount of code redundance (for a simple different color wood by example) is huge.

Anyway, thank you for you answer.

[diesieben07]

This has nothing to do with code redundance.

[Koward]

Oh, the fact that there is no "default in case of uninstalled mod" block yeah, I was referring to the fact we can't make a Block with only small property changes just by "extending" and overriding the previous one without any problem (keeping most original properties), or at least not in the vanilla way.

 

If I'm completely wrong don't hesitate to tell me to get out check whatever documentation. I don't want to waste your time.

[diesieben07]

There is no mechanism to store "fall back to this BlockID" in the world save format. Hence this is not possible.

[Koward]

And there is absolutely no way to create a Block with same ID but different metadata ? I understand new entry in registry => new ID, is that really the only way ? If only we could just add a line in the Enum..

Couldn't addSubstitutionAlias() be used for this purpose ? I never used it, so I don't know, and it looks like something bad, but the road to heaven is paved with bad practices or something like that.

[diesieben07]

No, what you want is not possible.

[Draco18s]

Just imagine two mods trying to do that at the same time.