Detector
A detector looks at what a monitor reports, or runs its own check, and decides if that looks like cheating.
When it does, it tells the AntiCheat-Monitor. The monitor adds that report to a threat score. You can react in the Inspector, in code, or with a punisher.
The AntiCheat-Monitor lists the detectors on it.
For most detectors, PossibleCheatingDetected stays true after the first find. The game-time detector is different: it clears that flag when the clock looks normal again.
Universal
| Detector | Free | Pro | What it catches |
|---|---|---|---|
| PrimitiveCheatingDetector | + | + | A protected value that was changed in memory |
| GameTimeCheatingDetector | + | A sped up, slowed, or stopped game clock | |
| DeviceTimeCheatingDetector | + | A device clock that was moved | |
| InputCheatingDetector | + | A button pressed faster than a person can |
Mobile
| Detector | Free | Pro | What it catches |
|---|---|---|---|
| MobileGenuineDetector | + | + | An Android or iOS build whose package name is no longer yours |
Android
| Detector | Free | Pro | What it catches |
|---|---|---|---|
| AndroidPackageTamperingDetector | + | A repacked app: wrong store, wrong file, wrong signature, or extra libraries | |
| AndroidDeviceCheatingDetector | + | Known cheat apps installed on the phone |
iOS
| Detector | Free | Pro | What it catches |
|---|---|---|---|
| IOSJailbreakDetector | + | Signs that the iPhone or iPad is jailbroken |
Desktop
These run on Windows, macOS, and Linux standalone builds.
| Detector | Free | Pro | What it catches |
|---|---|---|---|
| ModLoaderDetector | + | Mod loaders such as BepInEx or MelonLoader | |
| DebuggerDetector | + | A debugger attached to the game | |
| VirtualEnvironmentDetector | + | The game running inside a virtual machine |
Note
Desktop, Android, and iOS checks skip development builds and the Unity Editor unless you turn on Verify development builds for that platform.