mojira.dev
MC-248251

Loot table Inconsistencies

The loot tables for Logs and blacktone (for example) is exactly the same, yet logs always drop regardless of what you break it with, and blackstone only drops when you break it with a pickaxe despite the loot table not even having a "match_tool" check.

 

This is just one example but Im sure this happens with many other blocks as well.

 

This is an issue when it comes to datapack creation. Personally, I do not think it makes sense for wood to be able to be broken by hand, so I made a datapack where it uses a "match_tool" check to make sure logs can only be broken by an axe. This however, makes it no longer drop from explosions. Then I thought of the perfect solution; just copy the loot table of blackstone since it has the exact properties I'm looking for: it can only be broken by a certain tool, yet still drops from explosions. But to my disappointment, the loot tables are exactly the same when compared side by side.

Linked issues

Comments 3

The core of this report's issue is "whether or not a block loot table triggers is determined by the required tool, rather than the required tool being set in the loot table, and it always running on destruction". Changing this opens up issues with explosions though, as they don't use tools. Additionally, it is a change request and not necessarily a bug. (Block loot tables existed before you could change what blocks needed what tools to mine, something not being updated with newer things doesn't make it a bug.)

 

TLDR, I don't this this is a valid issue.

Thank you for your report!
However, this issue is Invalid.

You have posted a feature request or a suggestion. This site is for bug reports only.
For suggestions, please visit Minecraft Suggestions on Reddit or visit the Feedback website.

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

Thank you for your report!
We're tracking this issue in MC-138163, so this ticket is being resolved and linked as a duplicate.

That ticket has already been resolved as invalid. Please take a look at the parent ticket (MC-138163) and see if an explanation is provided there in the description of the ticket or in the comments for why this issue is invalid.

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.

aceplante

(Unassigned)

Unconfirmed

(Unassigned)

1.18.1

Retrieved