Describe the bug
I was doing quests in FTB Quests and then weird graphical bugs, and it crashed.

To Reproduce
I dont know.

Expected behavior
To not crash.

Version:

• Fabric
• v0.14.8

Additional context
https://bytebin.lucko.me/tAMXVpx1NT

That is unfortunate, but 1.18.2 is out of support, as I am supporting 1.19. 1.19 will not be "finished," in the way you mean, until Mojang starts working on 1.20, really, so if I waited till then I'd have to support two major versions at a time. If you wish to apply the fix yourself, recompile DynAssetGen, and redistribute it under the conditions of its license, feel free to do so; I only support one major version of Minecraft at a time, however, with the exception of major breaking bugs, and this one is obscure enough that I will not be backporting a fix unless some other major bug pops up in 1.18.2.

I need the full log, not just the crash report. What you have given me now is basically useless because it doesn't tell me what was registering stuff to DynAssetGen.

https://bytebin.lucko.me/HnWbn6Dk9A

Alright, I've got a few ideas. What were you doing in FTB quests when the crash occurred?

s when the crash occurred?

Ehm, i think look trough an item menu. Searched for ores.

Okay, so FTB quests somehow looked up a resource that doesn't exist. They shouldn't have done that, but that's a different issue

I can probably add a workaround to DynAssetGen; however, it will not affect your version because 1.18.2 is out of support.

How can 1.18.2 be out of support if 1.19 isnt finished yet? :I

What do you mean? 1.19 is finished.

Theres still not the final 1.19.X release, we modpack authors cant really update our packs to it, cuz last time we did, Mojang just broke everything from 1.18.1 -> 1.18.2. Now we need to live with bugs on 1.18.2, cuz authors stop supporting 1.18.2 ;(

I should also clarify: if someone else PRs a fix for this on 1.18, then I will publish a 1.18.2 release with the fix. I am simply not fixing it myself.