Detected or not — the honest version
Anyone who tells you a cheat cannot be detected is selling something. Anyone who tells you every cheat gets you banned tomorrow is selling something else. The truth sits in four concrete places, and three of them are about you.
What a ban actually depends on
- Signatures. A file whose hash or code shape is already in a database gets flagged on sight, regardless of how it behaves.
- Behaviour. Statistics that no human produces: identical flick times, perfect tracking through smoke, 100% headshot ratios over hundreds of fights.
- Reports. Players who die to something strange report the account. Reports queue a review, and a review that finds nothing still watches you.
- Who has the file. A public download is a sample. Every anticheat vendor can obtain one, run it, and add it to the list before you install it.
Kefir — the anticheat Rob Run runs on — states plainly that it buys popular cheats to study them. That is not rumour, it is their published policy. Any file sold to thousands of people is a file they already own.
What this build does about each one
Signatures: nothing sits on disk
The loader is one signed executable with an encrypted payload inside it. Nothing is written to disk until a licence key passes verification, and the payload that lands afterwards is re-derived per build, not shipped as a stable file. There is no install directory to scan, no DLL dropped next to the game, no registry key pointing at a runner.
Behaviour: the settings are the defence
A 4° FOV with 80 ms smoothing looks like a player who is good. A 30° FOV with zero smoothing looks like a machine, and no amount of code obfuscation changes what the killcam shows. The single largest ban factor in this category is not the software — it is the person using it at maximum.
Reports: play like a person
Do not track a target through a wall for ten seconds and then pre-fire them. Do not go 40-0 in a lobby of new players. Do not run the overlay on a stream where your name is legible. These are not technical failures; they are social ones, and they generate the reports that start every review.
Distribution: keys, not files
The build is not publicly downloadable. Keys are issued one at a time through Discord, bound to one machine on first activation, and the loader will not stage the payload for a machine it has not seen. A file that cannot be obtained cannot be sampled, and a sample that does not exist cannot be added to a signature list.
It does not mean zero risk. It means the risk is not the thing you were told to worry about. The realistic failure mode for a private build is behaviour and reports, not a hash match — and both of those are in your hands.
The habits that get people caught
- Rage settings. Maximum FOV, zero smoothing, head-only. It works, and it is why the account is gone in a week.
- Reusing a public loader. Free releases are the vendor's test corpus. They are not free.
- Sharing a key. One key, one machine. A key that appears on two hardware IDs is a key an admin can see.
- Streaming. Overlay visible, name visible, clip posted. That is a report with evidence attached.
- Obvious statistics. A fresh account with a 90% headshot rate across 200 matches gets reviewed whether or not anything was detected.
The part nobody writes down
Every account you attach this to should be an account you are willing to lose. That is true of every cheat ever made, at every price, in every game. A lifetime licence buys you the software forever; it does not buy you the account back.
What a private build buys you is time. Time before a sample exists, time before a signature is written, time before a review finds a reason. Spend it playing like someone who is not being watched, and the time lasts longer.
How the licence gate fits in
Verification happens before staging, in memory. The server signs a token tied to your hardware ID, the loader verifies the signature locally, and only then does the payload decrypt. A patched URL cannot mint a licence because the signature comes from a private key that never leaves the server. A copied token does not work on another machine because the payload key is wrapped against the hardware ID it was issued to.
After the first activation, a lifetime key receives a perpetual token and the loader stops contacting anything at all. No heartbeat, no telemetry, no phone-home during a match.
Keep reading
Keys are issued one at a time
Lifetime, bound to one machine, updates included. Message @kongthebest on Discord.
See access details