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
Kyori Adventure not usable in more than one Bungeecord/Waterfall plugin #1171
Comments
I also have this problem |
Solvable by using an older version of MiniMessage (4.12.0) and adventure-platform-bungeecord (4.2.0) e: nevermind it's not :( |
an temporary fix for this is maybe just using velocity instead :) but I will take a look at this |
well actually this looks like a classloader bug which has nothing in common with cloudnet |
Solution: downgrade adventure-platform-bungeecord to a version that matches cloudnet and shade it but exclude adventure-api. Yes, even if the version matches CloudNet's version. |
This is very likely a BungeeCord issue. This error does not occur on other platforms. But if exclusion works go with it I guess. The shaded version of adventure was bumped to latest in the nightly builds :) |
Stacktrace
Actions to reproduce
Use
adventure-platform-bungee
in one plugin (shaded ofc), do something with adventure components in another plugin depending on the first one.Tested with a basic default setup, a Lobby server (Purpur 1.19.3 for CN4, Paper 1.19.2 for CN3), and static waterfall-latest.
CN3
CN4
The mini plugin I reproduced this with can be found here:
https://github.com/itsTyrion/crashtest - I uploaded the compiled release incl the plugin with all the kotlin libs in releases.
For builds
gradle buildArtifacts
builds and collects the artifacts in adist
folder butgradle jar
in both modules works too.Kotlin isn't shaded with the current config tho - and it works in all plugins.made a 2nd branch that shades kotlin and uploaded that as as release, too
CloudNet version
Other
No response
Issue uniqueness
The text was updated successfully, but these errors were encountered: