Hello,

For some reason the variant blocks that contain the ore take far longer than they should to mine (something like 12 seconds to mine a marble copper ore with a diamond pickaxe) and it does not drop the ore. I tried looking into the config files as mentioned on the mod page but honestly I just can't make heads or tails of it lol. Any help is appreciated!

Thank you :)

Hmm... Something is causing the mining level tags to not be generated right, it seems. Can you provide a full log? May be some hints there.

I can certainly try! I'm sort of new to logs/troubleshooting, et al. so if this is the wrong document I apologize.

Thank you!
latest.log

That should be perfect! I'll try to get this figured out when I have the chance

Thank you!!

Hey, I don't mean to be a bother but have you got around to taking a look at this? No rush, I'm sure your life is busy enough as it is :)

Thank you!

You're all good! Take your time, your life is way more important than minecraft haha

Sorry, I've been quite busy. In theory I should have more free time in the next month or so

Hey, so it appears to be an issue with 1.20.6 as well.

Hmm. Possibly some wacky mod interaction, that's what caused this the last time I had the issue. I'll try to boot it up in the next week or so and figure it out.

Ah heck is this another issue with someone's tool tier defining that one bit as null that shouldn't be? I've got safeguards for that but I should be able to track down the exact issue with that in mind; may be a bit till I have a chance to poke it.

Well, since then I also realized that the blocks didn't even have loot tables, nor were registered in any tag. And either I did something wrong or the way the dynamic datapack is generated overrides it, but trying to add tags and loot tables by hand (i.e. via a save custom datapack) didn't do anything. Thus, while there is this null issue, the actual cause could lie much beyond that. Unless maybe this single null issue could be the cause of breaking the whole runtime datapack?

Hmm. I'll poke it when I have a sec.

After some looking into it, it would appear that it tracks down to the TieredItemMixin, where a hypothetical resource for tiered block break is referenced, but actually wouldn't exist, at least from my understanding. The issue log I have got from this, sadly, does not list issue causes, so the full stacktrace is not available, and same goes with @FruityLasagna 's.

It would, although, appear to happen at setting up the PathAwareInputStreamSource (see line 1325 of Fruity's log).

A way to work around it could be to dynamically generate a fallback, or at least catch the issue somehow to not let it hinder the mod's behaviour

getting this on 1.21.1 neoforge. Is there anything we can do to temp fix it?