When using the "item_specific_speeds" array of "minecraft:destructible_by_mining" block component for Add-on creating, sometimes the defined tool may not able to destroy the blocks. I also found this bug in some versions of Minecraft before.
The attachment has 3 parts: A vedio that describes this bug , a picture of a fragment of JSON that defines my customized block, and my Add-on that shows this issue.
Attachments
Comments 5
migrated
I have a similar problem. If I specify the item using
{"tags": "q.all_tags('minecraft:is_pickaxe', 'minecraft:iron_tier')"}The block breaks faster as expected, but if I use
"item": "minecraft:iron_pickaxe"it does not
Additionally, the block "glitches" when I try to break it with an iron pickaxe:
As if the client considers the block broken but the server doesn't, and re-places the block.
(The bug shown in the video only happens in the second case, with "item": "minecraft:iron_pickaxe" , and not with {"tags": "q.all_tags('minecraft:is_pickaxe', 'minecraft:iron_tier')"}, to be clear)
I have a similar problem. If I specify the item using
{"tags": "q.all_tags('minecraft:is_pickaxe', 'minecraft:iron_tier')"}The block breaks faster as expected, but if I use
"item": "minecraft:iron_pickaxe"it does not
Additionally, the block "glitches" when I try to break it with an iron pickaxe:
As if the client considers the block broken but the server doesn't, and re-places the block.
(The bug shown in the video only happens in the second case, with "item": "minecraft:iron_pickaxe" , and not with {"tags": "q.all_tags('minecraft:is_pickaxe', 'minecraft:iron_tier')"}, to be clear)