Closed AnttiMK closed 2 weeks ago
This should have been fixed with https://github.com/GeyserMC/Geyser/commit/b2619fa7c79e58fea9e05c68a5bd7a9ecc2b5f46, are you not up to date?
That commit did not fix that error message. It was ignored as I believe the error belongs in Floodgate. Conversation was had about the issue in #development earlier today.
Is a scheduled fix for this coming soon? Getting tired of seeing the endless console spam at my proxy lol
Sorry for the late response. We do plan on fixing this issue in the coming months, but it'll take some time because it's not an easy issue to solve
I have the same problem if you need something to testing i can help.
Are there any updates on this?
Unfortunately, no. If there are, we will inform here.
Problem is still here :(
The problem still exists with the most recent version
This should be fixed in the upcoming Floodgate 3.0 update. I'll keep this open until we're there.
I'm going to close this issue to mark progress to Floodgate 3.0. Starting in 3.0 Floodgate will be able to run inside Geyser, meaning that a separate Floodgate plugin is no longer needed for any setup that required both Geyser and Floodgate on the same server. Which also means that this issue will be fixed.
When using the Floodgate API, if Geyser and Floodgate are both installed on the proxy, the following exception is thrown whenever
getLinkedPlayer()
is called:As discussed on Discord, this seems to be a known issue. Probably not limited to the
LinkedPlayer
class, but instead to all classes in theorg.geysermc.floodgate.util
package.