This is another issue I've run into while connecting from a bedrock client (1.19.30) via Velocity proxy (3.1.2-SNAPSHOT-184) configured with the Geyser (Build 1195) and Floodgate (Build 73) plugins. This is with the latest Loohp Limbo server as of the time of writing.
The root cause is that the Bungeecord login (velocity config option player-info-forwarding-mode = "legacy") seems to
sometimes send a Floodgate key and sometimes it doesn't. I haven't been able to root cause why that is, but the consequence is that the case LOGIN: handler in ClientConnection.java which pulls the client IP addr from data[2] sometimes gets the ip addr, and sometimes gets the Floodgate cipher.
I spent a few hours digging around in the Velocity, Geyser, and Floodgate sources, but I'm not a Java expert and failed to find where the bungeecord-ified login message is constructed. In comparison, the Loohp Limbo login handler is super clear and straightforward, so I've just handled the "optional" floodgate cipher attribute being sent or not-sent there.
PR coming momentarily which fixes the problem for me.
This is another issue I've run into while connecting from a bedrock client (1.19.30) via Velocity proxy (3.1.2-SNAPSHOT-184) configured with the Geyser (Build 1195) and Floodgate (Build 73) plugins. This is with the latest Loohp Limbo server as of the time of writing.
The root cause is that the Bungeecord login (velocity config option
player-info-forwarding-mode = "legacy") seems to sometimes send a Floodgate key and sometimes it doesn't. I haven't been able to root cause why that is, but the consequence is that thecase LOGIN:handler inClientConnection.javawhich pulls the client IP addr fromdata[2]sometimes gets the ip addr, and sometimes gets the Floodgate cipher.I spent a few hours digging around in the Velocity, Geyser, and Floodgate sources, but I'm not a Java expert and failed to find where the bungeecord-ified login message is constructed. In comparison, the Loohp Limbo login handler is super clear and straightforward, so I've just handled the "optional" floodgate cipher attribute being sent or not-sent there.
PR coming momentarily which fixes the problem for me.