---
title: "Detections"
description: "What Asphyxia watches for, what happens when it finds something, and how to tune it."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.asphyxia.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Detections

A detection is one specific thing Asphyxia watches for. Each one either **bans**
immediately or issues a [strike](/anticheat/strikes), depending on how
conclusive it is.

Every detection can be switched on or off from your dashboard's
[Configuration page](/website/configuration). If one is causing trouble for a
single player rather than everyone, [whitelist](/anticheat/whitelisting) them
against it instead of turning it off.

## Client detections

These run on the player's machine and report back over
[the heartbeat](/anticheat/heartbeat).

| Detection | Watches for |
| :--- | :--- |
| No-Clip Detected | Moving through the world in ways normal movement can't produce |
| Vehicle NoClip | The same, while in a vehicle |
| Godmode | Health, armour or damage immunity beyond what the game allows |
| Teleport | Covering large distances instantly |
| Vehicle Boost | A vehicle moving far faster than its model can |
| Fast Run | On-foot movement speed beyond the game's limits |
| Infinite Stamina | Sprinting that never depletes |
| Infinite Roll | Combat rolling without the usual cooldown |
| Night Vision / Thermal Vision | Vision modes enabled outside of scripted use |
| Player Blips | Revealing every player's position on the map |
| Citizen AI Modifications | Tampering with the game's NPC behaviour |
| Plate Change | Changing a vehicle's plate client-side |
| Vehicle Repair | Repairing a vehicle client-side |
| Large Voice Proximity | Extending voice range beyond your server's setting |
| Incendiary Ammo | Ammo types the player shouldn't have |
| Blacklisted Weapon | Holding a weapon on your blacklist |
| Blacklisted Event | Triggering a client event you've blacklisted |
| Config Tamper | Editing the anti-cheat's own settings on the client |
| OCR Detection | Cheat-menu text visible on the player's screen |

## Server detections

These run on your server, where the client has no say at all.

| Detection | Watches for |
| :--- | :--- |
| Blacklisted Server Event | Triggering a server event you've blacklisted |
| Server Event Spamming | Firing an event far more often than legitimate use |
| Mass Vehicle / Ped / Object Spawning | Spawning entities faster than any normal script |
| Blacklisted Vehicle / Ped | Spawning a model on your blacklist |
| Vehicle / Ped / Object Whitelist | Spawning a model not on your whitelist |
| Vehicle Throw | Launching a spawned vehicle as a projectile |
| Invisible / Inaudible Explosion | Explosions altered to hide where they came from |
| Boosted Explosion Damage | Explosions doing more damage than the game allows |
| Boosted Camera Shake | Explosions with exaggerated screen shake |
| Explosion Spam | Explosions created far faster than normal play |
| Explosive Ammo | Explosive rounds the player shouldn't have |
| Steam Explosion Grief | A known griefing exploit using steam explosions |
| Heartbeat Integrity | A check-in that failed verification |
| Ban Evasion | A returning banned player — see [Fingerprinting](/anticheat/fingerprinting) |

## Ban or strike?

Roughly: **things only a cheat can do result in a ban; things a cheat usually
does result in a strike.**

Spawning a blacklisted vehicle is a ban — there's no innocent explanation.
Moving oddly for half a second is a strike, because a bad connection can look
the same. Detections that strike also require the behaviour to repeat before
they fire at all, so a single hiccup isn't enough.

## Tuning

Almost every detection has thresholds you can adjust on the
[Configuration page](/website/configuration) — how many entities count as
"mass" spawning, how fast is too fast for a vehicle, how many events per second
is spam.

Two rules of thumb:

- **Loosen a threshold before disabling a detection.** A detection that fires
  on 5% of players is usually mis-tuned, not useless.
- **Whitelist a person before disabling a detection.** If it's one developer
  tripping it, exempt that developer.

> **Note**
>
> Test on a live server with `asphyxia_debug` on. Detections fire and log
> normally, but nobody is banned or disconnected. See
> [Server configuration](/anticheat/server-config).

## Reacting in your own scripts

Every detection fires a server event before it's acted on, so another resource
can log it, alert staff, or record it elsewhere. See
[Events](/anticheat/events).

Source: https://docs.asphyxia.dev/anticheat/detections/index.mdx