Closed galacticwarrior9 closed 7 months ago
Relevant here are the log messages for the Spigot server. To verify, you are not receiving the "Incoming login request" log message for players with the newer protocol version? If that's the case we will need the ViaVersion too. FastLogin uses the standard plugin channels for communication, so I believe something goes wrong in translating this protocol.
Seems updating Velocity and/or ViaVersion resolved the issue - either that, or players moving onto 1.20.3+.
What happened?
New premium users connecting with 1.20.2 to my server - a network of 1.20.1 servers with ViaVersion running under Velocity - are not properly logged in.
In the Velocity logs, we observe:
For users who are logged in normally, we observe:
In other words, premium logins are never requested for the new 1.20.2 players. The problem does not correct itself and they are forced to connect with 1.20.1 or earlier versions.
Oddly enough, AuthMe on the auth server considers these players as logged in. But AuthMeVelocity does not, leading to the confusing situation in this screenshot:
In the auth server's logs, we see:
What did you expect?
Premium logins are requested for users connecting with 1.20.2.
Steps to reproduce
As far as I'm concerned, this only occurs to players who:
Plugin list
On the proxy: Plugins (24): AuthMeVelocity, BotSentry, CometSentinel, Constellation-GameLink, FastLoginVelocity, KeithAPI, LiteBans, LuckPerms, Maintenance, MCKotlin-Velocity, MiniMOTD, NuVotifier, Plan, ProxyQueues, ServerUtils,, SkinsRestorer, spark, TCPShield, Topaz, VelocityStaffChat, VLobby, VPacketEvents and VulcanVelocity
Configuration file
https://mclo.gs/5BHQUlj
Server log
See "What happened?" section.
Plugin version
1.12-SNAPSHOT-e15ea9c on both the proxy and auth server.
Platform
Velocity
Relevance
[X] I tried the latest build (build refers to development builds not necessary a release version)
[X] I checked for existing tickets - If there are, please vote them with a thumbs reaction and not create new ones