Players getting timed out
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.3k
- Forks
- 959
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 2
Description
Expected Behavior
Players should not be kicked randomly.
Actual Behavior
[00:04:57] [Netty epoll Worker #3/INFO] [com.velocitypowered.proxy.connection.client.ConnectedPlayer]: [connected player] Enderzombie44 (/163.117.104.252:50180) has disconnected: An internal error occurred in your connection.
[00:04:57] [Netty epoll Worker #3/ERROR] [com.velocitypowered.proxy.connection.MinecraftConnection]: [connected player] Enderzombie44 (/163.117.104.252:50180): read timed out
Players are getting kicked randomly.
Steps to Reproduce
Plugin List
There are no plugins currently installed.
Velocity Version
[11:49:33 INFO]: Velocity 3.3.0-SNAPSHOT (git-0cd069ec-b431)
[11:49:33 INFO]: Copyright 2018-2024 Velocity Contributors. Velocity is licensed under the terms of the GNU General Public License v3.
[11:49:33 INFO]: velocitypowered.com - GitHub
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
Start by reviewing the linked pastebin reproduction and the provided Velocity 3.3.0-SNAPSHOT logs, focusing on the read timed out disconnect from MinecraftConnection. Trace the relevant timeout handling and connection entry points in the Velocity source, then verify the fix by reproducing the random kick without plugins and confirming players remain connected.
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
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100