Cheater Finder (May not be accurate)

A client-side PvP analysis tool for Minecraft 1.21.11 (Fabric)

Cheater Finder watches the players who fight you and builds a statistical profile of how they play. It measures the things that are hard to fake — reach, aim precision, click rhythm — across every encounter, then tells you how unusual that player's numbers actually are.

It does not accuse anyone. It gives you data.

What it measures

Every time an opponent lands a hit on you, the mod records that moment from their side:

Each opponent gets a Suspicion Score (0–100) and a separate Confidence value based on sample size — so a player you've fought twice never gets treated like one you've fought fifty times.

Why the two numbers are separate

A high score on three hits means very little. A moderate score across two hundred hits means a lot more.

Cheat probability = Suspicion × Confidence

Confidence climbs with fights logged and hits recorded. A brand-new profile starts near zero no matter how bad the numbers look, which keeps one unlucky hit from branding someone.

Suspicion levels

Interface

Press C to open. (Can be changed in the controls)

• Searchable, scrollable list of every opponent you've encountered
• Click any player for their full breakdown across all fights combined
• Recording toggle — pause tracking whenever you don't want fights logged
• Live chat feedback when a fight starts, ends, or a sweep hit registers

Persistence

Profiles are keyed by UUID, not username — so a name change doesn't orphan someone's history.

Data is stored as raw per-hit records in cheaterfinder_data.txt, which means:

• Stats survive restarts and mod updates
• The file format is versioned and forward-compatible
• Scoring improvements retroactively re-analyse your existing history rather than freezing old numbers

Honest limitations

This runs entirely on your client, which puts real limits on what it can know. You should read the output with these in mind:

• Attacker attribution is inferred. The server doesn't tell your client who dealt the damage, so the mod picks the closest player who was mid-swing and facing you. Reliable in a 1v1, less so in a crowded fight.
• Missed swings are approximate. The client sees swing animations, not server-side hit results. If your opponent is also fighting someone else, their hits on that person register here as misses — which understates their accuracy rather than inflating it.
• Sweep detection is heuristic. Without a mixin on the sweep particle, it infers sweeps from damage magnitude and attacker posture. Other low-damage sources can occasionally trip it.
• Lag distorts reach. High-ping players will show inflated reach through no fault of their own. This is the single most common cause of a false positive.

Suspicion ≠ Proof

Unusual statistics are a reason to pay attention, not a verdict. Latency, playstyle, server tick behaviour, and small sample sizes all produce numbers that look wrong.

Use this to decide who's worth watching more closely — not to decide who's guilty.

Client-side only · Requires Fabric Loader 0.19.3+ and Fabric API · No server installation needed