MCPE-119294blocks tag components for custom blocks don't work
When setting up block tags for custom blocks, they don't work in game when using the appropriate tool. Blocks all break at the speed the "minecraft:destroy_time" component is set to.
When trying to break a block that uses the "stone tag", the block does not break when using the appropriate tool. If you were to make a wood block, using an axe would not break that custom block.
Linked Issues
Attachments4
Created Issue:
blocks tag components for custom blocks don't work
When setting up block tags for custom blocks, they don't work in game when using the appropriate tool. Blocks all break at the speed the "minecraft:destroy_time" component is set to.
Attachments1
C__Users_forge_AppData_Local_Packages_Microsoft.MinecraftUWP_8wekyb3d8bbwe_LocalState_games_com.mojang_development_behavior_packs_EndcreasedB_blocks_endmethyst_ore.json - Sublime Text (UNREGISTERED) 3_1_2021 6_18_25 PM.png
- Unresolved
- Open
- Unconfirmed
- Windows
- Windows 10 1909
- 1.16.210.61 Beta 1.16.201 Hotfix
![[MCQA] Kinga Izdebska](../../../data/avatars/users/18949.svg){kind=small}
When setting up block tags for custom blocks, they don't work in game when using the appropriate tool. Blocks all break at the speed the "minecraft:destroy_time" component is set to.
When setting up block tags for custom blocks, they don't work in game when using the appropriate tool. Blocks all break at the speed the "minecraft:destroy_time" component is set to.
When trying to break a block that uses the "stone tag", the block does not break when using the appropriate tool. If you were to make a wood block, using an axe would not break that custom block.
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
![[MCQA] v-magwar](../../../data/avatars/users/18935.svg){kind=small}
Yes, this problem persists
![[MCQA] v-weszaj](../../../data/avatars/users/18941.svg){kind=small}
I am sending a link to an exemplary addon, in which the "block tag" does not work, additionally I created an example pickaxe to which I added the ability to destroy an example block and it works on this pickaxe, and on Minecraft pickaxes it does not work.
https://www.mediafire.com/file/hdb0frq9xs35sn6/Sample_addon.mcaddon/file
The block can be found in the Construction category in creative mode or can be recalled by typing "sample:sample_block" and the pickaxe "sample:sample_pickaxe".
is duplicated by
is duplicated by
is duplicated by
Thank you for your report!
We're tracking this issue in MCPE-119294, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCPE-119294, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCPE-119294, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response
Is this still an issue in the latest version? If so, can you please add it to the affected versions (or mention it if you are not the reporter).
Also, just a reminder, to make your bug report as effective as possible, please try and include the following steps to reproduce the problem:
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Steps to Reproduce:
1. Create a custom wood block using an ADDON and in the 'minecraft:components' add "tag:wood": {}
2. In the 'minecraft:components' make the 'minecraft:destroy_time' equal to 2 (the same as a vanilla log)
3. Create a new world and /give yourself the block
4. Place it next to a vanilla log
3. Use a Diamond Axe to break both of them
Observed Results:
The Diamond Axe breaks the vanilla block at the expected speed but the custom wood block breaks at the same speed as if you were punching it with your fist.
Expected Results:
The Diamond Axe item should break all blocks tagged with the 'wood' tag at the same speed because inside its destroy_speeds it says that all blocks tagged with 'plant', 'wood', or 'pumpkin' would take the same amount of time.
Is this issue fixed on the latest version? Its still persists on 1.17.2.
Is this still an issue in the latest version?
Affects latest version 1.17.41
Hi
Does this issue still occur after updating to 1.18.2?
This ticket will automatically reopen when you reply.
Yes, this problem persists
Resolving temporarily as Awaiting Response. Could you please attach an example add-on to this ticket?
Sample addon.mcaddon
I am sending addon, in which the "block tag" does not work, additionally I created an example pickaxe to which I added the ability to destroy an example block and it works on this pickaxe, and on Minecraft pickaxes it does not work.
The block can be found in the Construction category in creative mode or can be recalled by typing "sample:sample_block" and the pickaxe "sample:sample_pickaxe".
This bug has still not been fixed as of the 1.19 update.
Can confirm this bug still exists in MC Bedrock 1.19.31. The following block data produces insta-mine blocks using vanilla pickaxes.
Using format 1.16.100 with experimental features.
{ "format_version": "1.16.100", "minecraft:block": { "description": { "identifier": "substances:aluminum_ore" }, "components": { "minecraft:explosion_resistance": 3, "minecraft:map_color": "#ffffff", "minecraft:loot": "loot_tables/aluminum_ore_loot.json", "minecraft:creative_category": { "category": "nature", "group": "itemGroup.name.ore" }, "tag:stone": {} } } }on version 1.19.40 it still does not work
I wonder when this will be fixed.
This is still an issue for current day minecraft 1.19.50+
1.19.62 it seems like the tags are half working.
If a custom block has "seconds_to_destroy" set to 15 and has "tag:iron_pick_diggable".
If the block has a tag searched for, then the block breaks at an increased rate (not the correct rate based on break time and tool speed).
I believe the issue is related to the break time calculation for custom blocks with tags and not tags not applying entirely.
I hope the above info helps to diagnose the problem so that we can just use a single speed calculation and not have to handle vanilla and custom blocks differently.
as for me, it still doesn't work, and besides, I don't know if it wouldn't be better to specify what tool should be used to destroy a given block or add this and that, i.e. tags for the block and the type of tool with which such a block should be destroyed
What they could do to fix this, is to make a new component for blocks, which could be called minecraft:on_player_destroying which could be similar to minecraft:on_player_placing.
Because, if you were to make an event, then do a sequence and then do a condition like query.get_equipped_item_name == 'diamond_pickaxe'. You could make it to where once it's being destroyed you could change the property of the block from true to false or so. Then you could just use permutations in order to detect if the property of the block is true or false. Then, you could change the block's mining speed using the component minecraft:destructible_by_mining. Now I feel like this could work as a temporary solution, for Mojang to add. While they actually fix the main issue.
Here's an example of what this could look like if it were ever added: