(No console errors were found other than client being told that velocity could not connect client to main server)
Bug Description
When attempting to a velocity proxy that is paired with an Paper 1.20.4 server running via* plugins, the 1.7.x clients instantly drop and cannot log in.
Steps to Reproduce
Create a velocity proxy with either offline mode or legacy forwarding,
Create a Paper 1.20.4 server with the via* plugins on it,
Try to connect to server with an 1.7.x client,
Get kicked out.
Expected Behavior
1.7.x clients can log in properly without issues.
Additional Server Info
Yes - This setup is using Velocity, (Build 316)
Paper 1.20.4 as backend server,
ViaVersion (4.9.3-SNAPSHOT), ViaBackwards (4.9.2-SNAPSHOT) and ViaRewind (3.0.6-SNAPSHOT).
This issue is similar to ViaBackwards' #663, only that it also affects 1.7.x clients.
EDIT: This not only affects velocity proxies but bungee itself as a whole.
Checklist
[X] Via plugins are only running on EITHER the backend servers (e.g. Paper) OR the proxy (e.g. BungeeCord), not on both.
[X] I have included a ViaVersion dump.
[X] If applicable, I have included a paste (not a screenshot) of the error.
/viaversion dump
Outputhttps://dump.viaversion.com/e69757425c33e0584c6b39d69ae7350ddedae20293b6a8fa5037ab081ba1dc09
Console Error
(No console errors were found other than client being told that velocity could not connect client to main server)
Bug Description
When attempting to a velocity proxy that is paired with an Paper 1.20.4 server running via* plugins, the 1.7.x clients instantly drop and cannot log in.
Steps to Reproduce
Expected Behavior
1.7.x clients can log in properly without issues.
Additional Server Info
EDIT: This not only affects velocity proxies but bungee itself as a whole.
Checklist