Asphyxia is a single FiveM resource that runs alongside your framework. It looks for cheating, records what it finds, bans the players responsible, and reports back to your web dashboard.
This section covers how the resource is structured, how to install and configure it, and how other resources can work with it.
How it works
Asphyxia runs in two places at once.
| Where | What it does |
|---|---|
| On the player’s machine | Watches for what cheat menus do, such as moving through walls, taking no damage, or spawning things that should not exist |
| On your server | Checks what players report, watches events and spawned entities directly, and makes every decision about bans |
A cheater can interfere with the part running on their own machine. They cannot make your server believe everything is fine, because your server keeps track independently. See the heartbeat.
Systems
Heartbeat
Confirms a player’s anti-cheat is still running.
Strikes
Warnings that add up, for behaviour that is not proof on its own.
Fingerprinting
Recognises a banned player who returns on a new account.
Global banlist
A shared list of cheaters caught across every Asphyxia server.
Triggers
Your own automation rules: when something happens, act on it.
Detections
What Asphyxia looks for, and what it does when it finds it.
Admin menu
Moderate from in-game, including the entity inspector.
Getting set up
Start with Installation, then set your server.cfg values. Troubleshooting covers the common problems.
Building on top of it
Other resources can react to what Asphyxia does, and ask it to act, through exports and events.