Kicked: Packet was larger than I expected

[x1p]

/viaversion dump Output

https://dump.viaversion.com/6d22b0e26eb7ae050bb44f589a51fb87bc4fd76d244aa9684483e329b5dbc4b0

Console Error

[20:30:13 INFO]: [Player123abc|/123.123.123.123:50807] <-> ServerConnector [test2] has connected
[20:30:13 INFO]: [/123.123.123.123:50807|Player123abc] -> UpstreamBridge has disconnected
[20:30:13 WARN]: No client connected for pending server!
[20:30:13 INFO]: [Player123abc|/123.123.123.123:50807] <-> ServerConnector [test2] has disconnected

Player kicked with message:

Bug Description

Viaversion won't let a player join if prefered server is not available.

Steps to Reproduce

1. Set up a bungeecord network (in this case WaterFall)
2. Edit the bungeecord/waterfall config.
3. Set the priority like this:

  priorities:
  - Test1
  - Test2

4. Make sure do power off Test1. So the client should be redirected to the next available server.
5. Join the network
6. Check if player is able to join.
7. Remove viaversion/viabackwards from proxy
8. Restart proxy and check if player is able to join.

Expected Behavior

Player can join without problem
When joining, he should get this message because the preferred server is down:

Additional Server Info

Waterfall: version git:Waterfall-Bootstrap:1.19-R0.1-SNAPSHOT:546fa12:495 by md_5
Paper: version git-Paper-10 (MC: 1.19) (Implementing API version 1.19-R0.1-SNAPSHOT) (Git: bd097b4)
Client: Native mc client version 1.19

Checklist

• Via plugins are only running on EITHER the backend servers (e.g. Paper) OR the proxy (e.g. BungeeCord), not on both.
• I have included a ViaVersion dump.
• If applicable, I have included a paste (not a screenshot) of the error.
• I have tried the latest build(s) from https://ci.viaversion.com/ and the issue still persists.

[Barvalg]

Please try the latest build(s) from https://ci.viaversion.com/

[x1p]

Thanks for the suggestion mr Bot. But ViaBackwards is running ViaBackwards-4.3.1-SNAPSHOT-268 which is up to date.
Nevertheless: ViaBackwards is irrelevant to this bug. This bug exists even without ViaBackwards running.

[Wolvend]

Having a similiar error as well. We're using Xcord (bungee) with a 1.18.2 purpur server with updated plugins & latest viaversion/viarewind. Seems to only give issues to 1.19 clients.
Removing viaversion gets rid of the issue

[kyzzf]

Had the same issue but my issue got closed for reason: not via's fault, lol!

[RTCFlyer]

Also encountering very similar issues, viaversion is installed on our proxy.
1.19 clients are getting this error on 1.18.2 purpur servers

[creeper123123321]

This might be related with the "couldn't connect" chat message packet sent by bungee while it's switching versions

[WongIong]

Same problem here, i have two plugins installed. Parties 3.2.6 and Viaversion ViaVersion/ViaVersion#617.
Waterfall ViaVersion/ViaVersion#497
Paper 1.17.1 - 411
Client 1.19
You could simply reproduce this error

I have already contacted the dev. from Parties, and he said that he using the Bungeecord message channel rightly so there must be something wrong with Viaversion.

[StoneMcYT]

Having a similar issue

Paper 1.19 78
Waterfall 498
Client 1.19

[Mapacheee]

Hi, i've this same issue
XCord 1.41
Client 1.19.2
Petal 1.19.2pre2

[haroldrc]

same

[LoboMetalurgico]

Same here, using Velocity