That means any operation can unnecessarily take an additional 50ms! This can be felt by some people in PvP, which is what this plugin aims to solve. The tick stack is processed 20 times every second. When new operations have to be carried out, they are added to the tick stack. The Minecraft server has a 'stack' of operations to carry out, called the 'tick stack'. The CPS limit in SmashHit will keep counting a player's CPS even if the limit is reached, however they will be denied further hits - this way a hacker spamming clicks will lock himself out of combat. SmashHit's configuration allows you to set your own preferred CPS. The CPS limit is automatically bypassed when we process hits on our own. * = This is the main focus of the plugin and is explained in the What does async hit pre-processing mean? section

There is a (pretty low) max clicks-per-second (aka CPS) limit hardcoded into the server.

Hits are processed in the current tick stack, not on demand *.

To my knowledge, there are two deficiencies:

There's nothing wrong with it, but it can be improved.

What's wrong with the default hit processor? This is currently the second release candidate for SmashHit, and is serving as a beta release. Source Code: Contributors: frash23 Note: this is not my plugin, I'm simply keeping it updated and fixing some bugs.

Download smash hit 1.0 0