Protocollib doesn't startup properly with Java 8, 11 and 16 openj9
pabloalba16 opened this issue ยท 5 comments
- This issue is not solved in a development build
Describe the bug
Latest Protocollib version (5.0.0 builds) doesn't load properly when SWM is also running on the server
To Reproduce
Steps to reproduce the behavior:
- Go to the jenkins build and download any of the 5.0.0 builds
- Add Protocollib and start the server with any of those mencioned Java
- You can see the error at the startup or at the logs
Expected behavior
A clear and concise description of what you expected to happen.
It should not give that error and allow other protollib's depend plugins to also load properly
Screenshots
If applicable, add screenshots to help explain your problem.
Here's the pastebin with the error
https://pastebin.com/nzCA5k7s
https://pastebin.com/Z2AJrNXJ
Version Info
Provide your ProtocolLib install info with /protocol dump through pastebin.
I can't as it does not load properly, it is the latest build, does not happen on 4.8.0 or previous versions
Additional context
Add any other context about the problem here.
My servers are using pterodactyI panel and i tested on both 1.8.9 and .1.12.2 and they display the same error as provided above
Man it's not my fault that to run plugins that depend on Protocollib i have to use the latest dev build no matter what server version i'm running
If a plugin that depends on ProtocolLib realy needs the latest dev build, even on servers older than 1.19... then the developer of that plugin did something wrong, I'm afraid.. :(
Since latest dev builds not yet properly support older versions (anymore?), the plugin must check for it and only use any new features with new version...
:(
But you are right, updates of ProtocolLib should not break compatibility to older mc-versions...
If a plugin that depends on ProtocolLib realy needs the latest dev build, even on servers older than 1.19... then the developer of that plugin did something wrong, I'm afraid.. :(
Since latest dev builds not yet properly support older versions (anymore?), the plugin must check for it and only use any new features with new version... :( But you are right, updates of ProtocolLib should not break compatibility to older mc-versions...
protocollib 5.0 includes packetevents 2.0 support so there's no other way