Closed onebeastchris closed 1 year ago
gunhippy
commented
2 years ago Experiencing the same issue. Server console doesn't give much to go on though. I've validated that the velocity side is ok as well as the proxylite plugin. Floodgate for spigot is working fine on paper servers so it's purely the floodgate-fabric side of things having the issue
onebeastchris
commented
2 years ago update: disabled send-floodgate-data, but still have floodgate -fabric on the backend - unlinked bedrock players see their skins, linked bedrock players don't
krisklosterman
commented
2 years ago I am having the same issue. When send-foodgate-data is true, no one can connect to fabric server. Using velocity as proxy.
zbx1425
commented
2 years ago Same issue.
onebeastchris
commented
1 year ago Currently only working workaround to get send-floodgate-data working is disabling global linking; that makes it work. I've done some research a while back, posted it on the PR that attempted to get support for FabricProxyLite; it seems like the message sent from Velocity's floodgate-velocity to floodgate-fabric is too long when linked info is included - atleast according to @Tim203 when I asked in the dev channel a while back
Here's my digging thus far: https://github.com/GeyserMC/Floodgate-Fabric/pull/70
onebeastchris
commented
1 year ago this was fixed in my PR; no idea why it's still open
Configuration: Velocity proxy (geyser on newest version + floodgate), with player-info-forwarding set to "modern", and floodgate data sending enabled Fabric Server (in the background): fabric-floodgate (with key from floodgate-velocity) + FabricProxy-Lite (with the key set up aswell)
Result:
https://mclo.gs/5o4tcx4 here's the log file - let me know what else to provide!
-> before adding floodgate on the side of the Fabric-server-side, everything was working -> FabricProxy-Lite is set up correctly (for usage without floodgate. couldn't find any info whether floodgate requires any modification there)