Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ProtocolSupport does not allow access to the server

See original GitHub issue

After updating GeyserMC and Floodgate plugins, they do not work with ProtocolSupport plugin.

ProtocolSupport causes an error like this:

[12:31:43] [Network Listener - #1/INFO]: [Geyser-Spigot] /XXX:XXX tried to connect!
[12:31:44] [Network Listener - #1/INFO]: [Geyser-Spigot] Player connected with username RetnaX6494
[12:31:50] [Geyser player thread-2-1/INFO]: [Geyser-Spigot] Attempting to login using floodgate mode... authentication will be encrypted.
[12:31:50] [defaultEventLoopGroup-4-1/INFO]: [Geyser-Spigot] RetnaX6494 (logged in as: RetnaX6494) has connected to the Java server
[12:31:50] [defaultEventLoopGroup-4-1/WARN]: [Geyser-Spigot] Downstream packet error! Invalid packet id: 26
[12:31:50] [defaultEventLoopGroup-4-1/INFO]: [Geyser-Spigot] RetnaX6494 has disconnected from the Java server because of Connection closed.
[12:31:50] [Network Listener - #1/INFO]: [Geyser-Spigot] Bedrock user with ip: /XXX has disconnected for reason CLOSED_BY_REMOTE_PEER

After removing ProtocolSupport you can play normally, but thanks to ProtocolSupport I had prefixes in floodgate, which he removes ProtocolLib: /

I tested both the latest version of ProtocolSupport 1.17.1-1 (https://www.spigotmc.org/resources/protocolsupport.7201/) and the development version from https://build.true-games.org/job/ProtocolSupport/

ver Geyser-Spigot [13:03:46] [Server thread/INFO]: Geyser-Spigot version 1.4.3-SNAPSHOT [13:03:46] [Server thread/INFO]: Website: https://github.com/GeyserMC/Geyser/blob/master/pom.xml [13:03:46] [Server thread/INFO]: Author: GeyserMC