Closed slash1div closed 5 months ago
We should wait limboapi 1.20.6 support.
This is still happening with latest Geyser and LimboAPI versions, both for 1.20.6 and 1.21 :(
@Rbot48, can you try to reproduce this issue with the latest dev-build?
@Rbot48, can you try to reproduce this issue with the latest dev-build?
Thanks for the prompt response! Unfortunately no, it is still happening:
[09:59:25 INFO] [geyser]: /ip:60487 has pinged you!
>....
[09:59:26 INFO] [geyser]: /ip:44865 tried to connect!
>....
[09:59:26 INFO] [geyser]: Is player data signed? true
>....
[09:59:26 INFO] [geyser]: Could not find packet for ClientToServerHandshakePacket
>....
[09:59:26 INFO] [geyser]: Could not find packet for ClientCacheStatusPacket
>....
[09:59:26 INFO] [geyser]: Player connected with username Rbot48
>....
[09:59:26 INFO] [geyser]: Rbot48 (logged in as: Rbot48) has connected to the Java server
>....
[09:59:26 INFO] [geyser]: Locale already loaded: en_us
>....
[09:59:26 INFO] [floodgate]: Floodgate player who is logged in as Rbot48 uuid joined
>....
[09:59:33 INFO] [geyser]: Scoreboard updater: took 1 ms. Updated 0 players
>....
[09:59:47 INFO] [geyser]: Scoreboard updater: took 1 ms. Updated 0 players
>....
[09:59:56 INFO] [floodgate]: Floodgate player logged in as Rbot48 disconnected
>....
[09:59:56 INFO] [geyser]: Rbot48 has disconnected from the Java server because of Read timed out.
>....
[09:59:56 ERROR] [geyser]: An exception occurred:
io.netty.handler.timeout.ReadTimeoutException: null
>....
[09:59:56 INFO]: [initial connection] /ip:0 has disconnected
>....
[09:59:56 ERROR]: io.netty.handler.timeout.ReadTimeoutException
I also tried with Geyser Standalone and only floodgate running on Velocity, but same behavior. Thank you
Mine has been working for around a week and my admin never told me. He said he reset the config without changing any of the settings, and it works. Try doing that. I don’t know if that’s the solution because my Pterodactyl’s logs got flooded from updating for 1.21.
That's odd. It's happening for me on a clean install with Geyser, floodgate and limboapi.
Wait, are you globally linked with Geyser? I just realized I was when the issue was happening.
Wait, are you globally linked with Geyser? I just realized I was when the issue was happening.
That's exactly it, thank you! @UserNugget the issue is only happening when a Bedrock account is linked to a Java account through floodgate. Unfortunately I can't just disable this linking since players would lose their progress
Okay, will check this out.
@Rbot48, latest dev-build should fix this issue, can you try to reproduce it again?
Describe the bug Connecting to a GeyserMC server with LimboAPI installed makes it unusable.
To Reproduce Steps to reproduce the behavior:
Expected behavior You should be able to connect to the server.
Screenshots
Server Info