FiveM anticheat on ESX, QBCore, vRP and standalone servers

An anticheat watches what players do. A framework decides what players are allowed to do. When the two disagree, you get either missed cheaters or banned innocents. This guide covers what to get right on the common FiveM frameworks, and what is the same everywhere.

Why the framework matters

On a roleplay server, a lot of legitimate gameplay looks like cheating to a naive anticheat:

• a mechanic script changes a vehicle's handling or engine power;
• a garage spawns a vehicle next to the player, a housing script teleports them inside;
• an admin uses noclip, god mode or spectate from the staff menu.

An anticheat that does not know your server sees "vehicle faster than stock" and "teleport". A good one understands where these come from, or lets you tell it.

ESX

• Versions: ESX Legacy is the maintained line. Very old ESX 1.x servers carry years of known exploitable events in their default resources; updating is the first security step.
• Inventory: many ESX servers replace the default inventory with ox_inventory or another one. Whatever you run, check that your anticheat supports it before you buy, and keep the inventory updated: item duplication bugs are fixed there.
• Events: ESX resources register many server events. Check the money and item events of every job and shop resource against the five checks in our event security guide.

QBCore and Qbox

• Callbacks: QBCore uses QBCore.Functions.CreateCallback heavily, Qbox uses ox_lib callbacks. Both are server events and need the same validation as RegisterNetEvent.
• Inventories: qb-inventory, ox_inventory and others hand out weapons as items. Check your anticheat supports the one you run, and that shops and stashes validate on the server.
• Admin menus: qb-adminmenu and similar menus give staff powers that look like cheats. Make sure your staff are recognised.

vRP and NDCore

The same principles apply: validate every event that grants money, items or vehicles, and make sure staff tools are not flagged. vRP servers often run heavily customised code; a log-first rollout (see below) matters even more there.

Standalone servers

Freeroam, PvP, racing and drift servers often have no framework at all. That makes some things simpler (no economy to protect) and others stricter: on a PvP server, combat cheats matter most, and you can usually afford tighter settings because fewer scripts do unusual things.

The same on every framework

Start order

Start the framework and its core dependencies (database wrapper, ox_lib, inventory) first. Where the anticheat goes depends on the product, so follow its install guide. Parity goes after your framework and your other resources:

ensure oxmysql
ensure ox_lib
ensure es_extended      # or qb-core / qbx_core / vrp / ND_Core
ensure ox_inventory
ensure [jobs]
ensure [shops]
ensure my-anticheat     # Parity: after the framework and your other resources

Roll out in log mode

Turn detections on in log-only mode for the first days. Watch what fires, find out which of your own scripts cause it, fix or exempt them, then switch to kick or ban. Rolling out straight into bans on a large roleplay server is how innocent players get banned in the first hour.

Know your staff

Every framework has a different idea of who is an admin (ACE groups, framework groups, Discord roles, txAdmin). Make sure the anticheat and the framework agree.

Keep a test server

Framework updates change events and behaviour. Test the update with the anticheat on a copy of the server before your players see it.

How Parity handles frameworks

Parity runs as one resource next to ESX, QBCore, vRP, NDCore or a standalone server. There is nothing to edit in your framework: you add the resource and its key file, and ensure it after your framework and your other resources.

Two things matter most for false positives:

• Permissions and Config Guard: give your staff the Bypass AntiCheat permission under Configuration → Permissions so their admin tools don't trigger detections, and Config Guard points out settings that are likely to hit innocent players.
• Server templates for Roleplay, Freeroam / PvP, Racing / Stunt and Standalone: pick the one that fits your server, and you see every change before you apply it.

A linked test server with its own key lets you try settings while test bans stay sandboxed. Have a look in the demo dashboard, or start with the FiveM server security guide.