Asphyxia is a single FiveM resource that runs alongside your framework. It watches for cheating on both the client and the server, keeps a record of what it finds, and enforces bans — while reporting everything back to your web dashboard.
The short version
The resource has two halves that check each other:
- On the client, a set of detections watch for the things cheat menus do — moving through walls, taking no damage, spawning things that shouldn’t exist.
- On the server, Asphyxia validates what clients report, watches events and entity spawns directly, and is the only side that can actually ban anyone.
A cheater can tamper with the client half. They cannot make the server believe the client is still healthy, because the server is the one keeping score — see the heartbeat.
Systems
Heartbeat
Confirms a protected client is still running, and carries detections back.
Strikes
Graduated punishment for behaviour that isn’t conclusive on its own.
Fingerprinting
Recognises a banned player who came back on a new account.
Global banlist
A shared list of cheaters caught across every Asphyxia server.
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. If something isn’t working, Troubleshooting covers the errors you’re most likely to hit.
Building on top of it
Other resources can react to what Asphyxia does, and can ask it to act, through exports and events.