Please consider reading all this post about the new packet limiting features.
Fixes:
- Offhand slot sometimes being seen (Matsv)
- Bossbars not sending correctly with multiple players via our API
- Idle not sending ground property for players (Fixes anti-cheat and block breaking issues potentially lots more)
First off, big thanks to JollyAjax for sitting with me at 1AM debugging to find the source of the block issues, thanks to him the issue is now located and fixes.
In this patch we've added a new
Packet Limiting System, this is there by default as a fail-safe to prevent proper abuse of packets being sent to a server overloading it.
We provide an option to set the maximum packets a client can send per second, which by default is 400. (Logging in can cause a lot of packet delay and a lot to be sent in a small amount of time). If you are getting people being kicked for "You are sending too many packets!" consider upping this value by 100 or so, but from testing it should be fine. (It's there to stop people sending 1000s)
We also allow you to monitor packets over a period of time. You set the amount you of packets per second to be considered as a warning and then choose how many warnings are allowed over a period of time.
By default we have a period of 6 seconds, the maximum warnings are 4. So you will be kicked if you send more packets than the warning level for 4 out of those 6 seconds. (By default it's 120 packets which from our monitoring the highest packets we've seen by vanilla clients is 80-90 by boats)
If you like this update etc, helps you stop hackers, nukers etc. Consider donating it's appreciated.
Report all bugs on our GitHub!
As a side note, if you don't understand what a packet is: It's a piece of information sent by the client when they move to notify the server that they are doing something, hacked clients can lag servers by spamming these packets.