getProtocolManager() is null
UsainSrht opened this issue ยท 6 comments
Is getProtocolManager() is null issue because of ProtocolLib or not?
I asked this to author of skacket and he said "ProtocolLib doesn't work in 1.17 currently. Waiting on a fix I reported then it will be updated." Protocollibs latest build was 526 when he said this.
Ok i figure it out for my self, that reason because the getProtocolManager() was null, i shade ProtocolLib to my FurnitureLib plugins what was the mistake i do. Sorry for that.
I get these error code https://paste.gg/p/anonymous/8a256a47ea4e4e4f8703767ba453eb63
The v2.7.0 released 5 days ago implemented support for Minecraft 1.17. I have no problems with the plugins using ProtocolLib.
It probably is a problem that Skacket uses the ProtocolLib API 4.6.1-SNAPSHOT.
These make no sense, thats not Plugins work like, it make no differents if you compile a plugin with v4.7.0 or v4.6.0
It looks like your plugins didn't use getProtocolManager() to register events what hear about incoming/outcoming packets.
As example my plugin is compiled with v4.7.0 but it dind't work with v4.7.0 and PaperSpigot 1.17.1