Login with Client 1.20.2 not possible #2
Comments
|
Please try the latest build(s) from https://ci.viaversion.com/. In case the issue still persists send the new dump |
%20behind.%20Please%20update%20to%20the%20latest%20version-orange?style=flat-square){kind=icon}
-1%20commit(s)%20behind%20master-yellow?style=flat-square){kind=icon}
|
I use the latest available version |
|
Please try the following two things individually:
The problem is that the changes in 1.20.2 break A LOT of plugins, and break expected behavior in proxies, so it's not easy to just definitively say what it is |
|
The first option doesn't make sense to me, so it's not acceptable, but it has to work like it used to. There has also been feedback in your Discord that it doesn't work either. We have already tried the second one with the same error. |
|
In my case, the players are getting instantly kicked with the 'Disconnected' message. ViaVersion is installed on the proxy. The following stacktrace is printed there It seems like on the 'subservers' (paper), the join event is even triggered and the player appears as connected for a brief moment, showing the 'Player x joined' and 'Player x left' messages. |
|
I've also tried moving ViaVersions to the subservers (removing it from the proxy), and now get the following error: |
|
It seems it might be related to https://github.com/NEZNAMY/TAB/releases/tag/4.0.4, I'll be testing it in few moments |
|
After running into this myself, I was able to reproduce this in a newly created testing environment. I am not super familiar with how ViaVersion works, but.. after some debugging To me it seems that there is some code missing to basically fake the I did not test connecting to a 1.20.2 upstream first, and then switching to a |
|
After updating some of my plugins, and updating both paper and bungeecord, this isn't happening to me anymore |
|
I still have the problem.
|
|
There is no benefit at all in running ViaVersion on the proxy other than having to place the jar multiple times. A lot of fixes are only available if run on the backend, and in general running on the proxy requires more complex handling of the client and puts more strain on it |
|
Nevertheless, it's stupid when you have to update a plugin that previously always ran via the proxy on 6 servers because you can't manage it. Bungeecrod now also works with TAB and Geyser without errors. So it's up to you somewhere why you can no longer come online with smaller versions. |
|
I can confirm I can't connect to Paper 1.20.1-196 with using Minecraft (1.20.2) to connect Waterfall (1.20) with ViaVersion (4.8.1). Adding ViaVersion into Paper server worked but it should work when adding it to Waterfall. Kicked whilst connecting to lobby: Outdated server! I'm still on 1.20.1 |
|
Update waterfall. |
|
I got the same problem but in mine it says that i can't connect with a version that is different from 1.18.2. Before the 1.20.2 release of bungee and viaversion this problem wasn't there. The hub is in 1.18.2, the survival is in 1.20.1, if i join with 1.20.1 it's all right, but when i try to join with 1.20.2 via versions says the error above (the version depends obv by the hub version) Latest version of Via Version (+115) |
To fix the problem the only way is to use via version and via backwards on all server, but before works perfect using it only on waterfall |
|
I have the same problème every i can't connect to my waterfall server in every versions after the update... please patch this ;-; bfore viaversion work perfectly... and when i set the plugin on the Backen server i can't connect on 1.20.2 to i can just connect on 1.20.1 ... |
There is a benefit in running ViaVersion on the proxy, especially for large networks where the admins could update only once after a new update is released rather than repeating the same operation on all backends. Also, if some behaviors were changed on the proxy for a long time, they should be adapted even if they seem to be broken. ViaVersion for 1.20.2 on Waterfall has been broken for two months and moving the plugin with its configuration to backends would only increase the maintenance cost for most servers, many servers have to move the plugin and its configuration to backends just to make sure their network is playable on 1.20.2. Please do something about this issue. |
|
That benefit is to a problem not unique to ViaVersion, and the reason that it runs on the proxy is not to make distribution easier. Large servers should have a templating system to allow for updating processes to be streamlined and not depend on Via running worse in every other way due to constraints that come with a proxy, especially Bungee Eitherway, please try updating ViaVersion to builds from https://ci.viaversion.com/job/ViaVersion-DEV/ as those have some important fixes to its state handling which should help, and make sure Waterfall and other proxy plugins are up to date as well |
/viaversion dumpOutputhttps://dump.viaversion.com/63cee61c1812b872d101ebc7cf9c401001d12c09de70d42503b0a384e2787422
Console Error
Bug Description
When I try to access the server with version 1.20.2 I get the message connection aborted
I hate this wrangling of authority. You say, Bungee's problem, Bungee says it's your business and I as a dev who would like to use your crap is the idiot. If there are problems, just try to solve them together and not just blame each other. It would help everyone in the MC world.
Steps to Reproduce
When I try to access the server with version 1.20.2 I get the message connection aborted
Expected Behavior
When I try to access the server with version 1.20.2 I get the message connection aborted
Additional Server Info
Via only on Bungee
Plugins:
BetterSecurity, BungeeChat, BungeePluginManagerPlus, BungeeSpy, BungeeTokens, CensorReloaded, CMIB, CraftingStore, DSGVO, ExceptionAnnouncer, floodgate, Geyser-BungeeCord, LiteBans, LuckPerms, Maintenance, MarriageMaster, NoVPN, NuVotifier, RankGift, RankUpgrade, spark, TAB, UltimateAutoRestartPassthrough, ViaBackwards, ViaVersion, cmd_alert, cmd_find, cmd_kick, cmd_list, cmd_send, cmd_server, reconnect_yaml.
Checklist
The text was updated successfully, but these errors were encountered: