Closed kusayu closed 2 years ago
That's not due to myLoot. myLoot is just in the error log because myLoot hangs the server thread waiting for the chunk a lootable container is in to finish loading - but the root cause is something else has caused a chunk to not load within the Minecraft Watchdog timeout, which defaults to 1 minute for a single tick.
See https://github.com/spoorn/myLoot/issues/17 and https://github.com/spoorn/myLoot/issues/16
I can look into some auto timeout logic, but it won't fix the root issue which is some chunk failed to load. Even without myLoot, you may still see crashes or performance issues.
Closing this in favor of https://github.com/spoorn/myLoot/issues/17
Modloader: Fabric 1.18.2 ver 0.14.5
Modpack AQM2
this is the crashlog
message.txt