-
-
Notifications
You must be signed in to change notification settings - Fork 89
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
Incompatibility with AsyncWorldEditInjector #973
Comments
Thanks for the detailed bug! Looking at the stack trace, it appears to be a similar issue with other plugins which change/break resource loading. AsyncWorldEditInjector appears to be open source, so I'll take a look to see if I can track down what exactly is causing this. |
@GedeonGrays This should now be resolved in the latest developer version. Can you please try updating and paste the output of what error is shown now? I'm expecting a message like I've looked into AsyncWorldEditInjector and it appears to contain a lot of reflection, hypothesis is it's somehow overriding a class which is causing this problem 🤔 |
Sure, I'll check it out soon. |
Yep, when starting the server with the latest developer version of BanManager and AWEInjector the following warning appears:
By the way, the same build of BanManager works fine without the AWEInjector, so the problem mentioned by @Letboes seems to be solved. |
Hello o/
I have a compatibility problem with AsyncWorldEditInjector.
Environment:
Server version: Uranium 1710-dev-5-B285-87f3435
BanManager version: Bukkit 7.6.0
AsyncWorldEdit version: 3.5.4 (the most up-to-date version for Cauldron-like servers)
AsyncWorldEditInjector version: 3.5.2 (automatically installed by AWE)
My actions:
As stated in the AWE installation instructions, I put the automatically installed AsyncWorldEditInjector into the mods folder (otherwise WE commands would not work on the server).
After starting the server BanManager reported the following error:
Of course, without AsyncWorldEditInjector BanManager works fine.
P. S. I am using BanManager version 7.6.0, not the latest, due to the problem mentioned by @Letboes in the #support channel of your Discord server.
P. P. S. I understand that I probably should have asked the AWE developers for a fix, but I'm afraid they no longer support 1.7.10.
So thanks in advance for your time.
The text was updated successfully, but these errors were encountered: