Console & Chat Commands

CXA Anticheat has a small set of commands for banning, kicking, screenshots and maintenance. You can type them in the server console, or in the in-game chat if your staff role allows it. This page lists every command with its parameters and the exact messages it prints, so you can search for them with Ctrl F.

Commands Need a Running Anticheat

CXA registers its commands only after the license has been verified and the anticheat has started. If the console shows no [CXA] License verified line, no CXA command exists yet. See License & Server IP.

Overview

CommandPurposeConsoleIn-gameDefault roles
cxaOpens the in-game panelNoYesowner, admin, moderator
cxabanBans an online playerYesYesowner, admin
cxabanofflineBans an identifier, online or notYesYesowner, admin
cxaunbanRemoves a banYesYesowner, admin
cxabaninfoShows the details of a banYesYesowner, admin, moderator
cxakickKicks an online playerYesYesowner, admin, moderator
cxascreenshotSends a screenshot of a player to the logsYesYesowner, admin, moderator
cxareloadReloads the ban list from storageYesYesowner
cxasyncPulls the latest configuration from the panelYesYesowner
cxainjectAdds Event Guard to your resourcesYesConsole onlynone
cxauninjectRemoves Event Guard from your resourcesYesConsole onlynone

How Commands Work

  • In the server console, or the txAdmin live console, type the command without a slash: cxakick 12 Spamming.
  • In-game, type it in the chat with a slash: /cxakick 12 Spamming.
  • Parameters are separated by spaces. The reason is everything after the other parameters, so it may contain spaces.
  • id always means the player's server ID, the number shown in the player list and in the in-game panel.
  • In the console, replies start with [CXA]. In-game, they appear in your chat with the alert prefix, [CXA] by default.
  • Messages follow the server's Language setting. This page shows the English texts.

If a command is not allowed, you get one of these replies:

ReplyWhy
You do not have permission to use this command.You have none of the roles selected for this command.
This command can only be used from the server console.In-game is turned off for this command, or it is a console-only command.
This command can only be used in-game.Console is turned off for this command, for example cxa.

Renaming and Disabling Commands

Open Configuration → Staff roles & commands → Commands in the panel. Each command has a row with Name, Console, In-game and Roles.

  • To rename a command, type the new name into Name, for example staffban instead of cxaban. Use letters, digits and _ only.
  • To disable a command, empty its Name. The panel shows "off" and the command is not registered at all.
  • Console and In-game turn the two places on or off. Roles decides who may use it in-game.

Click Save changes. Your server picks up the change within a minute and reloads the anticheat, which registers the new names. Staff Roles & Command Access explains roles and the full permissions table.

-- Inside Config.Permissions.Commands
Ban = { Name = 'staffban', Console = true, InGame = true, Roles = { 'owner', 'admin' } }, -- renamed
Screenshot = { Name = '', Console = true, InGame = true, Roles = { 'owner' } },            -- disabled

Command Reference

cxa

Opens the in-game panel.

Usage:

Console
/cxa

What happens:

  • The server checks that you have one of the roles of this command and at least one allowed panel action.
  • The panel opens with only the tabs and buttons your roles allow.
  • While you spectate a player, typing /cxa again stops spectating.
  • If Default key is set in Configuration → Staff roles & commands → In-game panel, the same key opens the panel.

Output: The panel opens. Without permission you get You do not have permission to use this command. In the server console the command answers This command can only be used in-game.

By default: in-game only, for owner, admin and moderator.

cxaban

Bans a player who is online right now.

Usage:

Console
# Server console: ban player 12 for 72 hours
cxaban 12 72 Aimbot on the highway

# In-game chat: ban player 12 permanently
/cxaban 12 0 Repeated cheating

Parameters:

  • id (number): The player's server ID. The player must be online.
  • hours (number): Ban length in hours. 0 = permanent.
  • reason (text): Everything after the hours. Optional; when empty, the reason is No reason given.

What happens:

  • CXA creates a ban with a new ban ID such as CXA-7KQ2MX and saves it in your ban storage (oxmysql or data/bans.json).
  • The ban covers the player's identifiers and hardware tokens, based on your ban matching settings. See Bans & the CXA Network.
  • The player is removed with the ban screen, which shows the ban ID, the reason, the end date and your appeal link if you set one.
  • The issuer is saved as Console or as the staff member's name and ID, for example Admin (3).
  • A Manual Ban entry is sent to the Bans webhook channel, and a short entry to the Admin channel.
  • Manual bans are never shared with the CXA network.

Output:

Output
[CXA] John has been banned. Ban ID: CXA-7KQ2MX

Missing or wrong parameters print Usage: /cxaban <id> <hours, 0 = permanent> <reason>. An unknown ID prints Player not found.

By default: console and in-game, for owner and admin.

cxabanoffline

Bans an identifier, whether the player is online or not. Use it for players who left before you could ban them.

Usage:

Console
# Server console: permanent ban for a Rockstar license
cxabanoffline license:1234567890abcdef1234567890abcdef12345678 0 Ban evasion

# In-game chat: one week for a Discord account
/cxabanoffline discord:123456789012345678 168 Threats against staff

Parameters:

  • identifier (text): A full identifier including its type, for example license:1234567890abcdef1234567890abcdef12345678 or discord:123456789012345678.
  • hours (number): Ban length in hours. 0 = permanent.
  • reason (text): Everything after the hours. Optional.

What happens:

  • CXA creates a ban that contains only this identifier. The identifier is used as the player name of the ban.
  • Every online player with exactly this identifier is removed right away.
  • When the player tries to join later, the ban stops them. With Extend identifiers on (the default), the other identifiers and hardware tokens they connect with are added to the ban.
  • An Offline Ban entry is sent to the Bans webhook channel, and a short entry to the Admin channel.

The identifier type must be one that bans are matched by, set in Match identifiers in Configuration → Ban system. By default these are license, license2, steam, discord, xbl, live and fivem (Config.Ban.MatchIdentifiers). An ip: identifier only works when Match IP is on.

Output:

Output
[CXA] license:1234567890abcdef1234567890abcdef12345678 has been banned. Ban ID: CXA-4TR8PN

A missing identifier, an identifier without : or missing hours print Usage: /cxabanoffline <identifier> <hours, 0 = permanent> <reason>.

By default: console and in-game, for owner and admin.

cxaunban

Removes an active ban by its ban ID.

Usage:

Console
cxaunban CXA-7KQ2MX

Parameters:

  • banId (text): The ban ID from the ban screen, the logs or the panel. Upper and lower case do not matter.

What happens:

  • The ban is removed from memory, so the player can join again immediately.
  • With oxmysql, the row in the cxa_bans table is kept and marked inactive. With JSON storage, the ban is removed from data/bans.json.
  • If the ban was shared with the CXA network, it is withdrawn there too.
  • A Ban Removed entry is sent to the Admin webhook channel.

Output:

Output
[CXA] Ban CXA-7KQ2MX has been removed.

Without a ban ID, the command prints Usage: /cxaunban <banId>. An unknown or expired ban prints Active ban CXA-7KQ2MX was not found.

By default: console and in-game, for owner and admin.

cxabaninfo

Shows the details of an active ban.

Usage:

Console
cxabaninfo CXA-7KQ2MX

Parameters:

  • banId (text): The ban ID. Upper and lower case do not matter.

What happens:

  • CXA looks up the ban and prints it in one line. Nothing is changed.
  • Date and Expires use the server's local time in the format YYYY-MM-DD HH:MM.

Output:

Output
[CXA] Ban CXA-7KQ2MX | Player: John | Reason: Aimbot on the highway | By: Console | Date: 2026-11-15 14:30 | Expires: 2026-11-18 14:30

A permanent ban shows Expires: Never (permanent). Without a ban ID, the command prints Usage: /cxabaninfo <banId>. An unknown or expired ban prints Active ban CXA-7KQ2MX was not found.

By default: console and in-game, for owner, admin and moderator.

cxakick

Removes an online player from the server without banning them.

Usage:

Console
cxakick 12 Stop spamming the radio

Parameters:

  • id (number): The player's server ID.
  • reason (text): Everything after the ID. Optional; when empty, the reason is No reason given.

What happens:

  • The player is removed and sees the kick screen: You have been kicked from this server. followed by the reason.
  • A Manual Kick entry with the reason and the issuer is sent to the Admin webhook channel.

Output:

Output
[CXA] John has been kicked.

Without an ID, the command prints Usage: /cxakick <id> <reason>. An unknown ID prints Player not found.

By default: console and in-game, for owner, admin and moderator.

cxascreenshot

Takes a screenshot of a player's screen and sends it to your logs.

Usage:

Console
cxascreenshot 12

Parameters:

  • id (number): The player's server ID.

Requirements: screenshot-basic must be running and Screenshots must be turned on in Configuration → System → Screenshots. See Screenshots.

What happens:

  • CXA asks the player's game for a screenshot and waits up to the screenshot timeout (6000 ms by default).
  • The picture is posted to the Screenshots webhook channel with the issuer's name. It is not shown in the console or the chat. To see the picture in-game, use Screenshot in the in-game panel.

Output:

Output
[CXA] Screenshot of John was sent to the logs.

Other replies: Usage: /cxascreenshot <id>, Player not found., Screenshots are disabled or screenshot-basic is not started. and Screenshot could not be taken.

By default: console and in-game, for owner, admin and moderator.

cxareload

Reloads the ban list from your ban storage.

Usage:

Console
cxareload

What happens:

  • CXA keeps all active bans in memory, so joining players are checked without a database query.
  • This command reads the bans again from the cxa_bans table or from data/bans.json. Use it after you changed bans directly in the database or the file.

Output:

Output
[CXA] Ban list reloaded, 12 active bans.

By default: console and in-game, for owner.

cxasync

Asks the panel for the latest configuration right now, instead of waiting for the next regular check.

Usage:

Console
cxasync

What happens:

  • The server contacts codexart.net immediately.
  • If a newer configuration is waiting and AutoReload is on in sv_config.lua, the anticheat reloads itself after 5 seconds and prints New configuration received from the panel, reloading the anticheat in 5 seconds.
  • If nothing changed, nothing else happens.

Output:

Output
[CXA] Requested the latest configuration from the panel.

You rarely need this command, because the server picks up saved changes within a minute anyway.

By default: console and in-game, for owner.

cxainject

Adds Event Guard to the resources on your server. Event Guard limits how often a player can trigger each server event of a resource.

Usage:

Console
cxainject

What happens:

  • CXA goes through every resource and adds this line to its fxmanifest.lua (or __resource.lua), right after the fx_version line: server_script '@cxa-anticheat/lib/eventguard.lua'
  • It skips cxa-anticheat itself, the resources in Never inject into, resources without server or shared Lua scripts, resources that already have the line and, if Skip escrowed resources is on, resources with a .fxap file.
  • It prints a summary, the changed resources and a restart reminder. Resources that could not be changed are listed as a yellow warning.
  • An Event Guard inject entry is sent to the Admin webhook channel.
  • The change only takes effect after the changed resources restart.

Output:

Output
[CXA] Event Guard injected into 14 resource(s), 2 already had it, 31 skipped, 0 failed.
[CXA] Injected: my-garage, my-jobs, my-shops
[CXA] Restart the server (or the listed resources) to apply.

In-game, the command always answers This command can only be used from the server console.

By default, Never inject into contains monitor, sessionmanager, mapmanager, spawnmanager, hardcap, rconlog, chat, yarn, webpack, baseevents, oxmysql and screenshot-basic. You change it in Configuration → Server detections → Event Guard.

Restart After Injecting

cxainject edits the fxmanifest.lua files of your resources. Restart the server afterwards so every changed resource loads Event Guard. If you update a resource later, its new fxmanifest.lua no longer has the line; run cxainject again.

Console only. It cannot be given to a role.

cxauninject

Removes the Event Guard line again from every resource that has it.

Usage:

Console
cxauninject

What happens:

  • CXA removes the @cxa-anticheat/lib/eventguard.lua line from every fxmanifest.lua (or __resource.lua) that has it, except for the resources in Never inject into.
  • It prints a summary, the changed resources and a restart reminder.
  • An Event Guard uninject entry is sent to the Admin webhook channel.
  • The server events of these resources lose their limit after the next restart.

Output:

Output
[CXA] Event Guard removed from 14 resource(s), 33 did not have it, 0 failed.
[CXA] Injected: my-garage, my-jobs, my-shops
[CXA] Restart the server (or the listed resources) to apply.

The second line uses the same Injected: label as cxainject, but here it lists the resources the line was removed from.

Console only. It cannot be given to a role.

Running Commands From Your Browser

Some of these commands can also run from your browser, without the server console. The Commands tab in the panel runs the equivalents of cxainject, cxauninject, cxareload, cxasync and cxaunban, and can send a message to every player. The Players tab can kick, ban, screenshot and message online players. Your server runs them within 30 seconds.

What a team member may run there depends on their role on the website, not on the in-game roles on this page. See Remote Actions.

Recommendations

Recommended:

  • Always write a reason when you ban or kick. It is shown to the player and stored in the ban.
  • Use cxabaninfo before cxaunban, so you remove the right ban.
  • Run cxainject once after installing new resources, then restart the server.
  • Keep cxareload and cxasync for the owner.

Avoid:

  • Using cxabanoffline with identifier types that are not in Match identifiers, such as ip: while Match IP is off. The ban would never stop anyone.
  • Renaming commands to names other resources already use.
  • Running cxauninject to fix a single resource. Add that resource to Never inject into and remove its line by hand instead.

Staff Roles & Command Access

In-Game Panel (/cxa)

  • The in-game panel offers kick, ban, unban and screenshots with buttons and shows screenshots directly.

Bans & the CXA Network

Event Guard

  • Event Guard explains what cxainject adds and how to tune the limits.

Remote Actions

Common Problems

The Command Is Unknown

What you see: The console or the game says the command does not exist.

How to fix it:

  • Check that the anticheat started. Without [CXA] License verified in the console, no CXA command is registered.
  • Check that the command was not renamed or disabled in Configuration → Staff roles & commands → Commands.
  • In the console, type the command without a slash.

"Player not found."

What you see: cxaban, cxakick or cxascreenshot answers Player not found.

How to fix it:

  • Use the server ID, not the character ID of your framework.
  • The player may have left. Use cxabanoffline with one of their identifiers instead.

"Active ban CXA-7KQ2MX was not found."

What you see: cxaunban or cxabaninfo cannot find the ban.

How to fix it:

  • Check the ban ID for typos. Ban IDs never contain 0, 1, O or I, so a ban ID with one of them was misread.
  • The ban may have expired already. Expired bans are removed automatically.
  • If you changed bans directly in the database, run cxareload first.

"Screenshots are disabled or screenshot-basic is not started."

What you see: cxascreenshot refuses to run.

How to fix it:

  • Add ensure screenshot-basic above ensure cxa-anticheat in server.cfg.
  • Turn on Screenshots in Configuration → System → Screenshots and save.

An Offline Ban Does Not Stop the Player

What you see: You banned an identifier with cxabanoffline, but the player still joins.

How to fix it:

  • Check that the identifier type is selected in Match identifiers in Configuration → Ban system. ip: only works with Match IP on.
  • Check that the identifier is complete and exact, including the type.
  • Check that the identifier is not in the bypass Identifiers list. Those players skip the ban check. See Staff Bypass.

Event Guard Is Not Active After cxainject

What you see: The console printed Injected: with your resources, but nothing seems limited.

How to fix it:

  • Restart the server. The line only loads when the resource starts.
  • Check that Event Guard is turned on in the panel.
  • For a resource that was listed under Failed:, check that the server may write to its folder, or add the line by hand as the first server_script.

© 2026 CodeXart Studios · CXA Anticheat