1 / 3Built interface — Flag overview
Overview
Cheat Detection Rulebook is a server-side detection layer for FiveM. It watches what the server can see, which is the only place a check cannot be patched out by a client menu: event rates per player, entities created without a matching script, weapons a player was never given, money that changed without a transaction, and position changes that no vehicle could explain. Each rule scores a flag rather than banning on sight, so a laggy player is not treated like a cheater.
When a flag crosses the threshold you set, the resource takes a screenshot through screenshot-basic, freezes the relevant state and writes an evidence bundle: the rule that fired, the values that tripped it, the player's recent events and the image. Staff review bundles in an in-game NUI console with a timeline per player, and the ban manager records the decision, the evidence reference and the appeal outcome so a second staff member can follow the trail.
The rulebook is written as data, not scattered checks. Every rule lives in a rules.lua table with its threshold, window, score and action, and framework bridges for ESX, QBCore and Qbox map money and inventory events to the same checks. Standalone servers get the event, entity and movement rules without the framework-specific ones. As new cheat menus appear and change what they touch, rules are revised and added, and the change is described in your Gaming Library.
The server-owner side of the plan is the operating material: a tuning guide for setting thresholds against your own player counts, a false positive checklist, an evidence retention note for staff, and an appeals process template. These are revised alongside the rules so the way you run reviews keeps pace with what the detections do, and a new staff member can read them and start reviewing.
What you get
- Rules for event spam, entity creation, weapon possession, money changes and movement
- Scoring with thresholds, windows and actions per rule so one flag never bans alone
- Screenshot on flag through screenshot-basic and an evidence bundle per incident
- In-game NUI review console with a per-player timeline and bundle viewer
- Ban manager with reasons, evidence references, durations and an appeals record
- Framework bridges for ESX, QBCore and Qbox plus a standalone rule set
- Discord webhook for flags and bans with the bundle reference in the message
- Tuning guide, false positive checklist and appeals template for staff
Eligible resources
The plan covers these resource types. Individual resources are listed in your Gaming Library as they publish.
- Detection rules
- Review console
- Ban manager
- Evidence bundles
- Framework bridges
- Staff runbooks
Features
- Scores, not snap bans
- Each rule adds to a score inside a time window, so lag spikes and edge cases are reviewed rather than punished on sight.
- Evidence you can follow
- Every flag writes a bundle with the rule, values, recent events and a screenshot, so a second staff member can check the call.
- Rules as data
- Thresholds, windows and actions sit in one rules.lua table, so tuning a rule is an edit rather than a rewrite.
Compatibility and requirements
Works with
- ESX, QBCore, Qbox or standalone, chosen in config
- screenshot-basic for screenshot on flag
- oxmysql for ban and evidence records
- Discord webhooks for staff alerts, optional
You need
- A FiveM server you control
- MySQL database reachable through oxmysql
- Staff who will review flags before bans are applied
Updates and content cadence
- The full rule set, console and ban manager from your first day
- Rules revised and added as new cheat menus and FiveM artifacts change
- Tuning guide, checklists and appeals template revised alongside the rules
License
- Licensed for one server network you own or operate.
- You may edit, re-texture and configure resources for that network.
- Reselling, sharing or re-uploading the files is not permitted.
Installation
- 1Download Cheat Detection Rulebook from your Gaming Library.
- 2Place the resource in your server's resources directory and run the bundled SQL.
- 3Set your framework, thresholds and webhook in config.lua and rules.lua.
- 4Add the ensure line to server.cfg after your framework core and screenshot-basic.
- 5Restart, then run in observe mode for a few days before enabling actions.
If you cancel
- Access and updates continue until the end of the period you paid for.
- The licence to run the rulebook ends with the subscription.
- Remove the rulebook from live servers once access ends.
More from DistroSource Gaming
Browse all
3FiveMSecurity
Anticheat & Protection
Server-side detections, an event guard and a live incident feed, updated as new FiveM exploits appear.
- Anticheat
- Detections
- Update plan
View details$158/mo
Subscription
3FiveMMLOs & Maps
MLO Vault
Every DistroSource FiveM interior in one library, with new MLOs each month.
- MLO
- Interiors
- Vault
View details$19/mo
Subscription
3FiveMUI & HUD
Interface Series
Player HUD, vehicle HUD, police MDT and dispatch in one maintained interface series.
- HUD
- MDT
- Dispatch
View details$16/mo
Subscription
$39/mo
Cheat Detection Rulebook
