Setting Up CXA Anticheat

CXA Anticheat installs like any other FiveM resource: you copy one folder to your server, add two lines to server.cfg (the file that tells your server what to start) and restart. Your settings live in the web panel, so you don't need to edit any Lua file to be protected.

Before You Start

You need an active license key, which looks like CXA-XXXXX-XXXXX-XXXXX-XXXXX, and a FiveM server with OneSync enabled. If you don't have a key yet, read License & Server IP first.

Requirements

RequirementWhy it is needed
FiveM server (FXServer) with OneSyncServer-side checks read entity, damage and explosion events that only exist with OneSync.
A CXA license keyThe anticheat checks the license when it starts and downloads your configuration from the panel.
Outgoing HTTPS access to codexart.netYour server verifies the license and picks up config changes over HTTPS.
oxmysql (optional, recommended)Saves bans in your database. Without it, bans are saved to data/bans.json.
screenshot-basic (optional)Needed for Screenshots and Live Screens.

CXA Anticheat works with ESX, QBCore, Qbox and standalone servers. It detects the framework by itself, so there is nothing to choose.

Setup Steps

Step 1 — Get the Files

Download the cxa-anticheat resource from the download link you received with your purchase. Keep the archive; you can use it again when you reinstall.

Step 2 — Upload the Folder

Extract the archive on your computer and upload the whole cxa-anticheat folder into your server's resources folder, for example resources/[security]/cxa-anticheat.

After the upload, the folder must contain:

  • fxmanifest.lua, config.lua, sv_config.lua and locales.lua
  • The client, server, lib, web and data folders

Upload the Whole Folder

Upload the folder in one go, or extract the archive directly on the server. Uploading files one by one through a web file manager often skips files, and the resource then fails to start.

Do Not Rename the Folder

The folder name must stay exactly cxa-anticheat. If it is renamed, the anticheat switches itself off and prints a red error in the console. This protects you from modified copies running under another name.

Step 3 — Add Your License Key

Put your key in server.cfg. This is the recommended way, because server.cfg is never sent to players.

# Your CXA license key. Use "set", not "setr" or "sets",
# so the key stays on the server and is never shown to players.
set cxa_license "CXA-XXXXX-XXXXX-XXXXX-XXXXX"

If you prefer, you can write the key into sv_config.lua instead. This file is server-only as well.

SvConfig.License = {
    Key = 'CXA-XXXXX-XXXXX-XXXXX-XXXXX',          -- Leave empty to use the cxa_license convar
    ApiUrl = 'https://codexart.net/api/anticheat',  -- Do not change unless support tells you to
    OfflineGraceHours = 72,                         -- Keeps protecting with the last config if our API is unreachable
    AutoReload = true,                              -- Reloads the anticheat when you save a new config in the panel
    UsePanelSecrets = true,                         -- Webhooks set in the panel override the ones in this file
}

Keep Your Key Private

Anyone with your key could try to start a server with it. Never post server.cfg or sv_config.lua in public channels, and never move the key into config.lua, because config.lua is a shared file that players can read.

Step 4 — Edit server.cfg

Add ensure cxa-anticheat after your database, your framework and screenshot-basic. CXA looks for these resources when it starts, so they must already be running.

# 1. Database (optional, lets CXA save bans in MySQL)
ensure oxmysql

# 2. Your framework, for example one of these
ensure qb-core
# ensure es_extended
# ensure qbx_core

# 3. Screenshots and screen monitoring (optional)
ensure screenshot-basic

# 4. CXA Anticheat: license key first, then the resource
set cxa_license "CXA-XXXXX-XXXXX-XXXXX-XXXXX"
ensure cxa-anticheat

# 5. Optional: let your admin group skip every check
add_ace group.admin cxa.bypass allow

The last line is optional. It uses ACE permissions (FiveM's built-in permission system) to stop the anticheat from checking your admins. Read Staff Bypass before you add it, so you know exactly who it covers.

Step 5 — First Start

Restart the server, not only the resource. Watch the server console. After a few seconds you should see lines like these:

Output
[CXA] License verified (remote), configuration v1.
[CXA] Illegal RPF scanner active without pure mode (sv_pureLevel 0), legal graphics mods can still join.
[CXA] Anticheat started | Framework: qbcore | Storage: oxmysql | Active bans: 0

If you see these lines, CXA Anticheat is installed and protecting your server. The framework, the storage type and the ban count match your own server, and the order of the lines can differ.

The First Server Binds the License

The first server that starts with your key binds the license to its IP address. Install the key on the server you want to protect, not on a test machine. To use a test server as well, you need a second license. See License & Server IP.

After the First Start

Open the Control Panel

  1. Go to codexart.net/anticheat/panel and sign in.
  2. Open your license.
  3. The Overview tab shows your server as online within a minute.

If the email you used at checkout belongs to your codexart.net account, the license is already linked and active. If not, redeem the key in the panel first. See License & Server IP for details.

Tell CXA Who Your Staff Are

Decide which staff members the anticheat should skip and which ones only get access to commands. Read Staff Bypass and Staff Roles & Command Access.

Review Detection Settings

Open Configuration in the panel and go through the client and server detections. On a new server, set detections that might clash with your scripts to log for a few days, check the logs, then switch them to kick or ban. Detections & Punishments explains each punishment, and Config with an AI Assistant shows how an AI assistant can tune the settings for your scripts.

Check That Everything Works

  1. Join your server.
  2. In the panel, open Players and check that you appear in the online list.
  3. If you have a staff role, type /cxa in the game chat to open the in-game panel.

Updating to a New Version

To update, replace the resource files with the new version and restart the server. Keep these two files from your old folder:

  • sv_config.lua, because it holds your license key and webhooks
  • data/bans.json, only if you store bans in JSON instead of MySQL

Your detection settings are stored in the panel, so they stay the same after an update.

Common Problems

"This resource must be named "cxa-anticheat""

What you see: The console prints [CXA] This resource must be named "cxa-anticheat" but it is "...". The anticheat is disabled until the folder is renamed and the server restarted.

How to fix it:

  • Rename the folder back to exactly cxa-anticheat, all lowercase, with a hyphen.
  • Change your ensure line to ensure cxa-anticheat.
  • Restart the whole server.

"No valid license key"

What you see: The console prints No valid license key. Set SvConfig.License.Key or add: set cxa_license "CXA-XXXXX-..." to server.cfg.

How to fix it:

  • Check that the set cxa_license line is above ensure cxa-anticheat.
  • Check the key for typos. Copy it from the panel instead of typing it.
  • Make sure the key is inside double quotes.

"License key is not redeemed yet"

What you see: The key exists but is not linked to an account yet.

How to fix it:

  • Sign in on the panel, redeem the key, then restart the server.

"This license is bound to another server IP"

What you see: The license was first started on a different IP address.

How to fix it:

  • Start the key only on the server it was bound to.
  • If you moved to a new host, open a ticket on your dashboard and we will move the license.
  • To run a second server, buy an additional license.

"License has expired" or "License is suspended"

What you see: The license is no longer active.

How to fix it:

  • Renew the license on the CXA Anticheat page. The server picks up the renewal by itself.
  • For a suspended license, open a ticket on your dashboard.

"Anticheat did not start: no verified license or configuration yet"

What you see: The server could not reach codexart.net and has no saved configuration to fall back on.

How to fix it:

  • Check that your host allows outgoing HTTPS connections. Some firewalls block them by default.
  • Make sure ApiUrl in sv_config.lua is still https://codexart.net/api/anticheat.
  • Restart the server once the connection works.

"oxmysql is not started, bans will be stored in data/bans.json"

What you see: CXA could not find oxmysql when it started.

How to fix it:

  • Move ensure oxmysql above ensure cxa-anticheat.
  • If you don't use MySQL, nothing is wrong: bans are saved in data/bans.json.

My Server Does Not Appear in the Panel

What you see: The console shows no errors, but the panel says the server is offline.

How to fix it:

  • Wait one minute. The server reports to the panel every few seconds after the license is verified.
  • Check that the license you opened in the panel is the same key that is in server.cfg.
  • Look for any [CXA] warning in yellow in the console and search for it on this site.

© 2026 CodeXart Studios · CXA Anticheat