Some bedrock players disconnected when changing server with Velocity

[Zhongzi8972]

Describe the bug

When some Players are changing server with a Velocity server, a error occured in velocity geyser. The player will diconnected from the server.
The error in the velocity console is:
[21:37:34 ERROR] [org.cloudburstmc.netty.handler.codec.raknet.common.RakSessionCodec]: [/112.12.135.37:9224] Error while ticking RakSessionCodec state=CONNECTED channelActive=true java.lang.NullPointerException: null

• This bug doesn't happen to every bedrock player. If a bedrock player triggered this bug, he/she could not change the server successfully no matter how many attempts are made, until the velocity server restart.

• This bug will prevent some bedrock players changing server, but it doesn't prevent these players logining in the first server with velocity----it only occur in the process of changing server.

To Reproduce

1. Logging in a server with velocity.
2. use /server xxx to change a server which connected with the velocity
3. A error occur in geyser-velocity, and the player is disconnected.

It couldn't reproduce 100% successfully, and it seems only occuring in certain server version.

Expected behaviour

No error occur.

Screenshots / Videos

No response

Server Version and Plugins

• Velocity version: velocity-3.4.0-SNAPSHOT-457
• The minecraft server version: Leaves version 1.20.6-215-master@e234432
• The bedrock client version: 1.21.41.01

Geyser Dump

https://dump.geysermc.org/Gr13iNNN0cL7Ss2eHRq6lDGAdgLaAKCJ

Geyser Version

2.5.1-b729 (git-master-b2045a5)

Minecraft: Bedrock Edition Device/Version

1.20.6

Additional Context

No response

[onebeastchris]

Please update Geyser, you're running quite a few commits behind. Further, please send a full server log showing the error

[Zhongzi8972]

Please update Geyser, you're running quite a few commits behind. Further, please send a full server log showing the error

Ok, I will update and try again.
And the log is the full server log about the error. It only displayed so much.

[onebeastchris]

This error should be harmless, as it's occurring after a player disconnects. It doesn't cause the disconnection itself

[Zhongzi8972]

Thank u, I will try more