In the constructor, the super(settings); call already sets this.getDefaultState() to be equal to this.stateManager.getDefaultState(), so they are functionally the same unless another mod modifies CarpetBlock's constructor.
super.appendProperties(builder); does not do anything unless another mod modifies it.
Only drawback is that it multiplies the amount of blockstates cover blocks have by 16 if Carpet Layers is present even though they are unusable. Other than that, the 2 mods work together as expected.
Closes #75
This pr should not modify normal behaviors since:
super(settings);call already setsthis.getDefaultState()to be equal tothis.stateManager.getDefaultState(), so they are functionally the same unless another mod modifiesCarpetBlock's constructor.super.appendProperties(builder);does not do anything unless another mod modifies it.Only drawback is that it multiplies the amount of blockstates cover blocks have by 16 if Carpet Layers is present even though they are unusable. Other than that, the 2 mods work together as expected.