Signs are destroyed by pistons and don't drop anything.
Can confirm, and this is only when a block is being pushed into a sign.
Cactus is destroyed by piston putting a block next to it…
Trouble is,
recipe_itemis used for two different purposes; the actual crafting recipe, and as thebase materialto copy properties, groups, sounds etc from.Can't read properties…
We are also missing the Cut (Red) Sandstone Slab, this would be one more line.
Trouble is, recipe_item is used for two different purposes; the actual crafting recipe, and as the base material to copy properties, groups, sounds etc from.
Can't read properties from…
Not sure what/why the
group:prefix in blocks like these:mcl_stairs.register_stair("sandstone", "group:normal_sandstone", {pickaxey=1, material_stone=1}, {"mcl_core_…
An ongoing Minecraft bug (MC-53641) suggests sandstone and quartz slabs have the wrong properties, and should both have the blast res. and hardness of…
Not sure what/why the group: prefix in blocks like these:
mcl_stairs.register_stair("sandstone", "group:normal_sandstone",
{pickaxey=1, material_stone=1},
{"mcl_core_sandstone_to…(Reverts are because I forgot to base this branch off master, so it used my last branch.)
I've stashed slabs and stairs changes for now, and a lot of blocks have 'wrong' hardness numbers, e.g. cut copper is too hard, smooth stone not enough. This could be fixed with the stairs + slabs…
Should I expand scope to include slabs and stairs? This would involve removing any hardcoded values, since the slab and stair code already uses a node parameter it gets default values from.
register_fence and register_fence_gate both have parameters for hardness and blast resistance, but these don't need to be removed if they just use the material as a default.
I was copying from register_fence, but will revert for now to avoid mod issues