1.15.2 unknown blockstate problems

[xX_deadbush_Xx]

I am making a custom log with four different types which each should have different textures. To do this I created a class that supers LogBlock and I added an integerProperty to the block. It gives me an unknown blockstate property warn in the console.

public class DreadwoodLog extends LogBlock {
    public static final IntegerProperty TYPE = ModBlockStateProperties.TYPE_0_3;
    
    public DreadwoodLog(MaterialColor verticalColorIn, Properties properties) {
        super(verticalColorIn, properties);
        this.setDefaultState(this.getDefaultState().with(AXIS, Direction.Axis.Y).with(TYPE, 0));
    }
    
    protected void fillStateContainer(StateContainer.Builder<Block, BlockState> builder) {
        builder.add(AXIS, TYPE);
    }

    public BlockState getStateForPlacement(BlockItemUseContext context) {
           return this.getDefaultState().with(AXIS, context.getFace().getAxis()).with(TYPE, 0);
    }
}
//in ModBlockStateProperties
public static final IntegerProperty TYPE_0_3 = IntegerProperty.create("type", 0, 3);

Console output: [...] ' for variant: 'axis=x,type=3': Unknown blockstate property: 'type'(edited)

 

could it be that the issue is caused by me supering LogBlock and overriding a bunch of methods? Its probably something really stupid but I just cant find the mistake...

[xX_deadbush_Xx]

It is still the same block with the same properties, I just want a different texture on each "type"

[Draco18s]

1 hour ago, xX_deadbush_Xx said:

It is still the same block with the same properties, I just want a different texture on each "type"

Welcome to The Flattening. Do not do this.

And yes, that's coming from me, where I basically did this, because I had a mechanical reason to use a block state (the variants were still valid), and boy howdy getting items to drop (for silk touch) was a bitch.

Edited May 24, 2020 by Draco18s