Block model types

blockModelType values are available through polymer and limited in number, since they re-use block-states that are visually the same on the client.

The following options are availble, with their amount:

See the polymer documentation for more infos about the properties of the block model types

When choosing blocks that break instantly on the client, like plant_block or tripwire_block for example, the destroyTime property in the block config has to be 0 as well.

You can map the blockModelType field of block configs to blockstates, this allows you to change the hitbox of the block depending on the block-state.

In some cases, for example when using the simple_waterloggable behaviour, you might want to specify the waterlogged state for your custom block.

{
  "id": "mynamespace:half_slab",
  "blockTags": ["minecraft:climbable"],
  "blockResource": {
    "models" : {
      "waterlogged=false": "minecraft:custom/block/dirt/dirt_slab",
      "waterlogged=true": "minecraft:custom/block/dirt/dirt_slab"
    }
  },
  "itemResource": {
    "models" : {
      "default": "minecraft:custom/block/dirt/dirt_slab"
    }
  },
  "behaviour": {
    "simple_waterloggable": {}
  },
  "blockModelType": {
    "waterlogged=false": "sculk_sensor_block",
    "waterlogged=true": "sculk_sensor_block_waterlogged"
  },
  "properties": {
    "blockBase": "minecraft:dirt"
  }
}

As of filament 0.16 it is possible to flag the block as virtual, to allow for an unlimited amount of block states. See Blocks for details.