ESX • QBCore • Qbox compatible
Instant download
Updates included
Discord support
Secure checkout

FiveM AntiCheat

Resource folder: gs_anticheat

View product

Installation Instructions for FiveM AntiCheat

Follow these steps to install and configure gs_anticheat on your FiveM server.

  1. Download the Resource
    • Go to portal.cfx.re
    • Navigate to Assets > Granted Assets > gs_anticheat
    • Download the resource
  2. Extract the Files
    • Open the downloaded .zip file
    • Inside, you'll find a folder named gs_anticheat
    • Move the entire gs_anticheat folder into your desired server resources folder (e.g., /resources/[scripts])
  3. Add to Server Configuration
    • Open your server.cfg
    • Add the following line:
      ensure gs_anticheat
  4. Restart the Server
    • Restart your FiveM server (Important!)
  5. Configure the Script (Optional)
    • Navigate to gs_anticheat/config.lua
    • Edit the configuration options to fit your server's needs

Does gs_anticheat work on QBCore?

Yes. The only hard requirement is ox_lib. It works on QBCore, ESX, and standalone servers as long as ox_lib is installed. Setup is mostly drag-and-drop.

How do I unban a player who was banned by mistake?

Use the server console command:

/gs_removeban [banId]

Ban IDs are stored in the gs_anticheat_bans database table.

Is there a web panel to view bans?

No built-in UI exists. Bans are stored in the database. Query the gs_anticheat_bans table through phpMyAdmin, HeidiSQL, or your preferred database tool.

Legitimate players are getting banned for weapon events

Another script (for example vMenu) may be triggering weapon remove events that look like exploits. Set Config.PreventWeaponEvents = false in config.lua, or keep detection on but change Config.WeaponEventAction to 'log' instead of ban.

Players get banned while using mission or creator scripts

Scripts that spawn many entities quickly (for example missions_creator with dozens of peds) can trip entity limits. Whitelist the ped models in config or raise thresholds in Config.EntityLimits.

Blacklisted vehicles like tanks or buzzards are not being blocked

Vehicle entries in config must use backticks (hash syntax), not quotes:

-- Wrong
['BUZZARD'] = { action = 'cancel', name = 'BUZZARD' },

-- Correct
[`BUZZARD`] = { action = 'cancel', name = 'BUZZARD' },

Cheaters are launching or exploding cars

gs_anticheat blocks prop, vehicle, and ped spam from cheaters, but it cannot detect noclip or player cloning. For mass explosions, many servers add a server-side handler:

AddEventHandler('explosionEvent', function(sender, ev)
    CancelEvent()
end)

Rate-limit bans on explosions tend to cause false positives, so blocking explosions entirely is usually safer.

Is there a command to scan the whole server for cheaters?

No. The anticheat blocks blacklisted entity spawns at creation time. It cannot retroactively detect arbitrary cheats. Available admin commands include:

Command Purpose
/gs_ban [playerId] Ban by server ID
/gs_removeban [banId] Unban
/gs_refreshbans Reload bans from database
/gs_blockentities [playerId] Temporarily block entity spawn
/gs_unblockentities [playerId] Remove spawn block
/gs_entitycleanup [playerId] Delete recent entities from a player

Can bans be sent to Discord instead of checking SQL?

Not by default. Add custom logging in bridge/sv_bridge.lua through the provided hook functions.

What does this anticheat actually protect against?

It focuses on server-side detection of common exploit patterns: entity spam, weapon events, super punch, and blocked prop or model spawning. It maintains ban checks on join and uses a large blocklist of known abusive models. It is not a full client-side anti-cheat and will not catch every type of cheat.