Config Editor

The Configuration tab holds every CXA Anticheat setting: detections, punishments, staff roles, lists and logging. You change them in your browser, press save, and your server picks up the new configuration within a minute, without restarting your server and without editing config.lua by hand.

Do Not Buy Ready-Made Configs

CXA has no ready-made config service, and anyone selling "ready CXA configs" is a scammer. A ready-made config cannot exist: every server has its own framework, scripts, events, vehicles and weapons, so the configuration has to be built for your server. To build one quickly, use Config with an AI Assistant.

How It Works

  1. Your configuration is stored with your license on codexart.net. Every save gets a new version number, for example v13.
  2. Your server checks the panel every few seconds. When the version changed, it downloads the new configuration.
  3. CXA reloads itself with the new values. With a license, the panel's values override the config.lua file on your server.

The editor has two modes, switched at the top of the tab:

  • Visual editor: every setting with a label, a short explanation and the right control (switch, number, list).
  • Code view: the same configuration as a config.lua file you can copy, download, edit elsewhere and import again.

Both modes show the same draft. A change you make in the visual editor appears in the code view right away. The panel remembers which mode you used last.

Visual Editor

Sections

The sidebar on the left groups the settings into sections. A number next to a section shows how many unsaved changes it contains.

SectionWhat it contains
GeneralLanguage, branding and framework.
Staff & BypassWho is never checked and who manages the anticheat.
Staff roles & commandsWho can use which command, from the server console or in-game, and what each role can do in the in-game panel.
Ban systemStorage and matching rules of bans.
ConnectionChecks that run while a player is connecting.
Network & trustCXA network features: global bans, account trust and server health warnings.
Game files (RPF)Catches illegal RPF mods without pure mode, so legal graphics and sound mods still join.
LogsDiscord, console and panel logging.
SystemScreenshots, entity lockdown and client settings.
Client detectionsChecks running on players' game clients.
Server detectionsChecks running on your server, impossible to bypass from the client.
Network & rulesFiveM network hardening, your own security rules and web monitoring.
ListsBlacklists used by the detections.

Every setting is described in All Settings.

Finding a Setting

Type in the search box at the top, for example noclip or webhook. The search looks at the setting names, their explanations and their config keys in both languages, and shows matching settings from all sections at once. The section name appears above each result.

Each setting shows its config key in small grey text under its name, for example Monitoring.MapInterval. This is the same key you see in the code view and in config.lua.

Groups, Switches and PERF Badges

Settings are grouped into cards, for example one card per detection.

  • A switch in the top right corner turns the whole group on or off. The badge next to the title shows On or Off, and the settings of a group that is off are dimmed.
  • A PERF badge marks settings that cost server or client performance. The amber note under the title explains the cost. Read it before you turn the setting on, and see Performance Tuning.
  • A detection card usually contains Punishment, Ban duration, and often Check interval, Tolerance and Screenshot. Detections & Punishments explains each of them.

Lists, such as blacklists, have two views. Chip view shows each entry as a tag; type a new entry and press Enter (comma separated entries work too). Bulk edit shows the whole list as text with one entry per line, which is faster for long lists.

Saving Your Changes

  1. Change one or more settings. A small dot appears next to every changed setting.
  2. A bar appears at the bottom of the page with the number of unsaved changes, for example 3 unsaved change(s).
  3. Press Save changes. To throw your changes away, press Discard.
  4. The panel confirms with Saved as v13. Your server applies it within a minute.

Before saving, the panel checks every value. If something is wrong, it shows 2 invalid value(s), check the highlighted fields., opens the section of the first problem and writes the reason in red under the setting, for example Maximum is 30. Nothing is saved until all values are valid.

If you try to leave the page with unsaved changes, your browser asks you to confirm.

Code View

The code view shows your whole configuration as a read-only config.lua file. It includes your unsaved changes, so it always matches what you see in the visual editor.

Every setting has a short English comment, and settings marked [PERF] carry their performance note. The file starts with this header:

-- ============================================================
--  CXA ANTICHEAT - CONFIG (generated by codexart.net panel)
--  Read-only export. Edit it anywhere (or with an AI tool) and
--  paste it back with 'Import code' in the panel to apply.
--
--  Punishment: 'ban' | 'kick' | 'warn' | 'log' | 'none'
--  BanDuration is in hours, 0 = permanent.
--  [PERF] = may raise server resmon on high population servers.
-- ============================================================

Config = {}

Further down, each section looks like this:

Lua
Config.Monitoring = {
    LiveMap = true, -- Live map
    MapInterval = 2, -- Map update interval
    Screens = true, -- Needs screenshot-basic.
    MaxScreens = 4, -- Players watched at once
    Fps = 1.0, -- Frames per second
    Quality = 0.35, -- Image quality
}

The toolbar above the code has these buttons:

ButtonWhat it does
Go to section…Jumps to a top-level block such as Logs or ClientDetections.
Wrap / No wrapWraps long lines or keeps them on one line.
Copy allCopies the whole file.
DownloadSaves the file as config.lua.
Import codeOpens the import window. Only shown when you can edit.

Above the code you also find the Build your config with an AI assistant card, see Config with an AI Assistant.

Importing Code

Import code lets you paste a configuration you edited outside the panel, for example in a text editor or with an AI assistant.

  1. In Code view, press Import code. The window opens with your current configuration already filled in.
  2. Replace it with your code, or edit it in place.
  3. Press Validate. The panel reads the code and lists the result:
    • Valid. 4 change(s): followed by the config key of every changed setting.
    • 1 invalid value(s): followed by each key and the reason.
    • No differences from the current draft. when nothing changes.
  4. Read the change list. If it is what you expected, press Apply to draft.
  5. The changes are now in your draft, not saved yet. Check them and press Save changes.

How it works: The import only reads plain values: tables, text, numbers and true / false. Nothing is executed. Functions, variables, local lines, require and loops are rejected with an error. Keys that CXA does not know are ignored.

You don't need to paste the whole file. A partial import changes only what you paste:

Lua
-- Only these two log settings change, everything else stays as it is
Config.Logs = {
    Panel = true,             -- Send detections to the panel's Detections tab
    DetectionCooldown = 30,   -- Seconds before a repeated log detection of the same player is logged again
}

-- A single value works too
Config.Monitoring.Fps = 0.5

Lists Are Replaced, Not Merged

When you paste a list, for example Config.BlacklistedVehicles = { 'rhino' }, it replaces the whole list. Paste the complete list if you only want to add one entry.

A partial import is merged into the last saved configuration, not into your unsaved draft. Save or discard your open changes before you import only a part of the file.

How Changes Reach Your Server

Your server talks to the panel every few seconds. After you save, this happens:

  1. On its next check, the server sees the new version number and downloads the configuration.
  2. CXA prints this line and restarts only the cxa-anticheat resource, not your whole server:
Output
[CXA] New configuration received from the panel, reloading the anticheat in 5 seconds.
  1. After the reload, the License verified line in the console shows the new version, and the Overview tab shows it as Config version.

To push a change right away, an owner or admin can press Sync configuration under Commands, or you can type cxasync in the server console. See Remote Actions.

Two settings in sv_config.lua on your server control this:

OptionKeyDefaultWhat it does
Automatic reloadSvConfig.License.AutoReloadtrueReloads the anticheat when a new configuration arrives. With false, the new configuration is stored and applied at the next restart of the resource or server.
Offline grace periodSvConfig.License.OfflineGraceHours72If codexart.net cannot be reached, the server keeps protecting with the last verified configuration for this many hours.

If codexart.net is unreachable, changes you save in the meantime reach your server as soon as the connection is back.

Read-Only Access

Viewers can open the Configuration tab, search it, use the code view, copy and download the file. They cannot change anything. The tab shows "You have read-only access to this configuration." and Import code is hidden.

Owners, admins and editors can edit. See Team Access.

Secrets Stay Out of the Config

Discord webhooks, the Steam API key and the VPN API key are not part of the configuration. They never appear in the visual editor, in the code view, in the downloaded config.lua or in the text you copy for an AI assistant. You set them under Webhooks & keys, or in sv_config.lua on your server. See Logging & Discord.

Recommendations

Recommended:

  • Set new or risky detections to log for a few days, check the Detections tab, then switch them to kick or ban.
  • Download the code view before large changes, so you have a copy to import again.
  • Change one area at a time and save, so the Activity tab shows clear steps.

Avoid:

  • Importing code from strangers or "config shops". Only import code you or your team wrote for this server.
  • Raising settings with a PERF badge without reading the note.

Config with an AI Assistant

  • The Code view contains a ready prompt that lets an AI assistant tune the config to your own scripts.
  • Its answer comes back through Import code, so you always see the change list before saving. See Config with an AI Assistant.

Team Access and Activity

  • Only owners, admins and editors can save. See Team Access.
  • Every save is recorded in the Activity tab with the changed keys and who saved them.

All Settings

Common Problems

My Change Does Not Reach the Server

What you see: You saved, but the server still behaves the old way.

How to fix it:

  • Wait a minute, then look for the New configuration received from the panel line in the server console.
  • Check that the server is online in the Overview tab and that Config version shows the new number.
  • If SvConfig.License.AutoReload is false, restart the cxa-anticheat resource yourself.
  • As an owner or admin, press Sync configuration under Commands, or run cxasync in the console.

"Someone else saved the config meanwhile. Reload to see their changes."

What you see: Saving fails because a team member saved a newer version.

How to fix it:

  • Open Code view and press Copy all to keep your changes.
  • Reload the page to load the newer version.
  • Import only the part you changed and save again.

"Some values are invalid." or Fields Marked in Red

What you see: The panel refuses to save and marks settings in red.

How to fix it:

  • Read the red text under each setting, for example Minimum is 1. or Must be a whole number.
  • If the error says a command or panel action uses unknown role(s), you deleted or renamed a staff role that is still used. Remove the role under Configuration → Staff roles & commands → Commands and In-game panel too.

"Only assignments to Config are allowed"

What you see: Validate stops with a message like Line 3: Only assignments to Config are allowed (found 'SvConfig') or Local variables are not supported, only Config assignments.

How to fix it:

  • Every line must start with Config, for example Config.Logs = { ... }.
  • Remove local variables, functions, if blocks and loops. The import only accepts plain values.
  • Never paste sv_config.lua. It holds your secrets and is not part of the configuration.
  • Variables inside values are not allowed either: write Fps = 0.5, not Fps = myValue. Otherwise you see Variables and function calls are not allowed ('myValue').

"Expected ',' or '}'" or "Unfinished string"

What you see: Validate shows a line number and a syntax error.

How to fix it:

  • Go to the line in the message. A comma between two entries or a closing quote is usually missing.
  • Check that every { has a matching }.
  • The import accepts up to 512 KB of code. A larger file shows Input is larger than 512 KB.

Import Code Is Missing

What you see: The code view has no Import code button.

How to fix it:

  • Your role is viewer, which is read-only. Ask the owner or an admin to change it under Team.

© 2026 CodeXart Studios · CXA Anticheat