Velocity server change issue

[ZuRiKanHD]

Expected Behavior

If Velocity is supposed to connect a player to another server, the player will be disconnected from the server they were previously on.

Actual Behavior

With the new build (491), Velocity doesn't disconnect from the old server, so the old server only disconnects after a timeout. This ensures that HuskSync, for example, doesn't detect the server change, and thus, synchronization of inventory, Enderchest, and so on isn't possible. While the player is active on the other server when switching servers, the previous server doesn't know that the connection has been lost and eventually times out.

Steps to Reproduce

See console log of the server to be left when changing servers

Plugin List

Velocity Version

Additional Information

No response

[bridgelol]

Also experiencing this

[electronicboy]

Can you reproduce without plugins?

[Krymonota]

I can confirm that I also had this problem with build 491 (ref #1380). Switching back to build 490 fixed the problem.

@electronicboy It's also reproducible without plugins if you use /server to switch to another server. You will see {username} lost connection: Timed out in the logs of the previous server, and other players will see the disconnected player until the timeout.

[bridgelol]

It's related to the following commit: https://github.com/PaperMC/Velocity/commit/a549880df1a7454799d30be57b9b7df4cb5c43b7

Without, it all works the way it should

[astei]

I think I know why this happening, but I need to see logs. There's already #1546 that's connected to io_uring. I'll disable its use for now.

[bridgelol]

I will also mention, it might be a coincidence but we only experience trouble on proxies running on AMD CPUs, intel (i9-14900k) does not give us the same issue

[LoyalPineapple]

I can confirm that I also had this problem with build 491 (ref #1380). Switching back to build 490 fixed the problem.

@electronicboy It's also reproducible without plugins if you use /server to switch to another server. You will see {username} lost connection: Timed out in the logs of the previous server, and other players will see the disconnected player until the timeout.

I will also mention, it might be a coincidence but we only experience trouble on proxies running on AMD CPUs, intel (i9-14900k) does not give us the same issue

is that literally AMD issue?

[tygh89071388]

I'm still encountering the same issue while using velocity-3.4.0-SNAPSHOT-514. From time to time, when players switch servers, the disconnect event doesn't get triggered properly on the original server.

Is there any solution to this problem?

[LoyalPineapple]

I'm still encountering the same issue while using velocity-3.4.0-SNAPSHOT-514. From time to time, when players switch servers, the disconnect event doesn't get triggered properly on the original server.

Is there any solution to this problem?

What is your CPU also what plugins do you use for player data transfer?

[tygh89071388]

I'm still encountering the same issue while using velocity-3.4.0-SNAPSHOT-514. From time to time, when players switch servers, the disconnect event doesn't get triggered properly on the original server. Is there any solution to this problem?

What is your CPU also what plugins do you use for player data transfer?

AMD9950X husksync

[Maximan2233]

I'm still encountering the same issue while using velocity-3.4.0-SNAPSHOT-514. From time to time, when players switch servers, the disconnect event doesn't get triggered properly on the original server.

Is there any solution to this problem?

Al parecer lo solucionaron en SNAPSHOT-#536 verificare su funcionamiento.