Custom blocks in 1.16.200.51 support custom geometry, but entity_collision and pick_collision only support a single basic block, and that block cannot be rotated or pivoted,and with the removal of blockshape setting, it is impossible to create an entity_collision configuration that behaves like a stair block.
In general, a block model and the entity_collision are likely to be identical, and where they are not, they are still likely to consist of more than one cube definition. Why limit entity_collision to a single block definition? Why reinvent the wheel for geometry functionality?
If you make entity_collision and pick_collision use standard minecraft:geometry files, or allow these two properties to support multiple cube definitions similar to a geometry file, or at the very least support rotation and pivot for these cubes, you open the door for easily making custom stairs and other shapes that do not conform to a simple block shape.
Please sign in to leave a comment.
2 Comments