Closed candy999 closed 9 months ago
The logs does not indicate that connection is made with raknetify. Please try reproduce without raknetify.
+1 I got the same issue… Can't reproduce without raknetify. Velocity 3.2.0-296 Raknetify 0.1.0+alpha.5.109 (EDIT: I updated raknetify to 0.1.0+alpha.5.113 and the issue still persists) Other plugins: luckperms, carbonchat, geyser, nanolimbovelocity, librelogin, vpacketevents, signedvelocity, tab, velocitycoollist, viaversion, viabackwards
Cannot reproduce with raknetify as the only plugin on velocity and a vanilla 1.20.1 server as the backend. Can this issue be reproduced with raknetify as the only plugin on velocity?
Ye 1.20.1 works fine, but now i upgraded to 1.20.2 (both client and server) and facing this issue. This error could be easier reproduced when going through portals (at least for nether portal, the end untested).
Can reproduce.
It seems that Velocity did not properly update their Respawn
packet for 1.20.2 update:
1.20.1: https://wiki.vg/index.php?title=Protocol&oldid=18375#Respawn
1.20.2: https://wiki.vg/index.php?title=Protocol&oldid=18641#Respawn
The fields are reordered but velocity still used the 1.20.1 format for 1.20.2+: https://github.com/PaperMC/Velocity/blob/07a525be7f90f1f3ccd515f7c196824d12ed0fff/proxy/src/main/java/com/velocitypowered/proxy/protocol/packet/Respawn.java#L162
Raknetify uncovers this issue because it makes Velocity actually decode Respawn packets. By default velocity does not decode them.
Closing as PaperMC/Velocity#1142 is resolved.
Describe the bug Someone asked this question from raknetify https://github.com/PaperMC/Velocity/issues/1142
To Reproduce Steps to reproduce the behavior:
Runtime info (please complete the following information):
ver
branches)Crash reports / logs
add -Dvelocity.packet-decode-logging=true
Other mods
Checklist
Additional context