Velocity server change issue
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.3k
- Forks
- 959
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 2
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is identified. Start by reproducing the server switch with build 491 and inspect the console log of the server being left. Done means the previous server detects the disconnect promptly instead of waiting for a timeout, so plugins such as HuskSync can detect the server change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100