PrismarineJS / PrismarineJS/node-minecraft-protocol
How to not kick the client when the server send too many packets to it ?
Open
Nobody has claimed this yet.
question
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 290
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 7
Description
This happens when sending lot of chunks to the client. It gets disconnected.
Increasing kickTimeout fixes it.
I guess the problem is the server can't send the keep alive packet fast enough, and then doesn't get the answer from the client.
How can this be fixed ?
Contributor guide
No contributing guide indexed for this repository
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 reproducing the disconnect while the server sends many chunks, then trace the server's keep-alive handling alongside kickTimeout. The issue is resolved when heavy packet traffic no longer causes a healthy client to be kicked for missing the keep-alive response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100