Jitter, Butterfly, and Drag Clicking Explained for Admins

What are jitter, butterfly, and drag clicking?

Jitter, butterfly, and drag clicking are input techniques that change how clicks and aim look from the server's side. Jitter adds small, fast aim movements. Butterfly clicking alternates two mouse buttons rapidly so attacks overlap in time. Drag clicking holds the button and slides it quickly across a surface. Some players use these techniques legitimately, so anticheats judge timing and variance over many clicks rather than one rate.

What does the server actually see?

The server never sees the mouse. It sees swing packets, interaction packets, and rotation updates. Each technique shows up as an unusual timing or rotation pattern in those packets. The same pattern can come from a player who simply clicks fast, which is why a single number is not enough.

• Jitter: small rotation changes that repeat quickly and return near the same spot.
• Butterfly: attack timing that overlaps heavily between sequences.
• Drag clicking: many attack or use events in a short window with very even spacing.

How do the patterns compare with honest play?

The table lists what each technique leaves in the data and the honest activity that can look similar. Use it to write review notes, not to convict a player.

How do you tune CPS checks without punishing fast players?

Tune checks with data from your own players. Collect timing from staff who use normal mice and a range of click styles, then see which checks flag them. Change one setting at a time, and keep alert-only mode until the review is complete.

• Collect attack timing from several staff members with different click styles.
• Confirm which check flags each pattern, using the check name in the alert.
• Look at the spread of clicks over several minutes, not one burst.
• Adjust one threshold in small steps, then rerun the same staff sessions.
• Keep alerts on review until the false-positive results are clear for your players.

# Replace the check name with the CPS or click check your anticheat reports.
grep -i "<cps-check-name>" logs/latest.log | wc -l

Why is a single CPS limit a weak rule?

A single rate limit misses patterns that repeat over time, and it flags fast honest players who cluster their clicks. Combine timing variance, rotation patterns, and staff review. Your anticheat's documentation explains which checks it runs and how it reports them.

Which click settings should you review first?

Review any input tools your server allows before you tune CPS checks. Some players use macro software or input remappers for ordinary reasons, and those inputs can look like autoclicking. Write down the input tools your rules allow so reviewers can compare them with an alert. Review that list once a season, since new input software can change how clicks appear in the data.

What have we not verified?

We have not tested any anticheat's click or jitter detection, and this article does not give CPS thresholds. Mouse hardware, client settings, and playing style change the numbers. Use your own staging data before you rely on any alert. Keep the input tools and client settings used in each staff session with the results, so a later review can compare like with like. Record which staff member ran each session, so a result can be traced back.