-
-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash with EWG #71
Comments
Can you test on Tuinity? I would bet this is due to their changes. EWG likely does some sketchy NMS that is broken by Spottedleaf's optimizations. |
Can confirm I get the same error on Purpur and Tuinity, but not paper (1.16.2/3). |
The problem is EWG devs dont understand how to properly detect Paper instances. Purpur is a Paper instance, but EWG does not see it as such. Instead, EWG sees Purpur as a generic Bukkit instance. This is a crucial difference because Bukkit bundles in a java library called FastUtil and they relocate it to a bukkit package. Paper removes the relocation so the package is in the normal place. This means, on Paper and all its forks (Tuinity, Purpur, etc) FastUtil is at its normal location. But EWG errors because it's trying to use FastUtil as Bukkit's relocated location due to EWG's improper Paper detection. There is nothing I can do to fix this on Purpur's end. It is purely on the plugin side to fix. Good luck, though. EWG devs are notorious for things like this. |
Random very weird Server Crash when genearting an EpicWorldGenerator World.
i first opened it on the EWG Issue tracker but it seems to only happen to purpur.
jonryf/EpicWorldGenerator-bugtracker#126
The text was updated successfully, but these errors were encountered: