- CPS (clicks per second) is a HUD module that counts your mouse clicks in real time and shows the number on screen as you play.
- It only reads local input and draws text, so there is nothing for an anticheat to flag.
- It is the opposite of an autoclicker: it measures clicks you already made, not new ones it manufactures.
CPS stands for clicks per second, and as a Minecraft module it is a small HUD readout that counts how fast you are clicking and prints the number on screen in real time. Instead of alt-tabbing to some external click-counter website mid-game, you get a live number anchored near your crosshair or sitting in a HUD corner, refreshing every second you keep clicking. It is a measurement tool, not a mechanic. The module watches input you are already generating and reports it back to you. It does not touch the input itself.
How it works
CPS counts mouse-button presses inside a rolling one-second window and writes the running total to the HUD. Every click bumps the counter for whichever window is currently open. Once a second elapses, the display swaps to the new total and starts counting again. Because the window keeps resetting instead of averaging over some longer stretch, the number tracks your actual clicking pace, not a smoothed-out figure from ten seconds ago.
The module never gets between your mouse and the server. Read an input event, increment a counter, draw a string, that is the entire pipeline. A click that fires still reaches the server as exactly one click: same timing, same packet, same everything. Rose is one client documented shipping a CPS readout, and it lives in the visual category next to other on-screen displays rather than anywhere near combat or movement, because it does not do anything to combat or movement.
Is it safe to use
Yes, cleanly. A CPS counter reads local mouse input and renders a number on your own HUD, full stop. It never sends an extra packet, never alters what the server receives, never touches a value the server would use to resolve an action. There is simply nothing here for a server-side anticheat to evaluate, because the feature never leaves your machine.
The confusion with autoclickers is understandable since both terms involve click speed, but they sit on opposite ends of the same idea. An autoclicker generates clicks on its own and is a genuine, bannable cheat. A CPS counter does the reverse: it measures clicks a human already made. One produces input, the other just reports on it.
Where Opal spends its module budget
Opal does not ship a dedicated CPS counter. That is not an oversight so much as a budget decision: the module reports a number and changes nothing about the fight itself, it does not land an extra hit or shave a millisecond off anything the server measures. Opal's combat and movement modules exist to move the needle in an actual fight. A click counter is more stream flex than edge, and Opal spends its module count on the latter.
FAQ
No. It only displays a number on the HUD based on clicks you already made. It does not change click timing, damage, or anything the server processes.
No, they are opposites. A CPS counter measures input you already generated, while an autoclicker generates input on its own. Autoclicking is a cheat. A CPS display just does math on clicks you made yourself.
No. It only reads local input and renders it on your own screen, so there is nothing for a server or anticheat to detect or flag in the first place.
Most commonly as a small readout near the crosshair or tucked into a HUD corner, updating continuously while you click. Exact placement depends on the client's HUD layout.
Higher legitimate click speed matters in click-based combat, so players use the counter to track technique, like butterfly or jitter clicking, and measure progress in real time instead of alt-tabbing to a website.
