[odd bug] Crash reports (possibly) falsely blaming malum for causing a crash
Shibva opened this issue ยท 1 comments
To reproduce: (hopefuly based on interaction)
-
install Blockswap with Malum
-
configure it to do a simple block replacement, BUT INTENTIONALY malform the json5 config paramiter
-
start and watch it crash (or it load fully with a "resource fail" error if you have resourcepacks configured
-
Observe crash report as it blames a render event for some reason; therefore showing that its blaming malum for some reason when the fault was with blockswap.
Ive seen this before I think with coldsweat when using it on neoforge for 1.20.1 though I'm not 100% sure. This tells me that something malum is doing during loadup is making the crash-report think malum is causing it, as both have the same error regarding the same render event
Evidence