In-Game Panel (/cxa)

The in-game panel is a staff window inside the game. You open it with /cxa and use it to watch, move, freeze, revive, message, screenshot, kick and ban players, and to browse and remove bans. Each staff member only sees the actions their staff role allows.

Requirements

You need a staff role that may use the In-game panel command (by default owner, admin or moderator). The Screenshot action also needs the screenshot-basic resource and Screenshots turned on in Configuration → System → Screenshots.

How It Works

  • When you type /cxa, the server checks your roles. If you may use the command and have at least one allowed action, the panel opens with only the tabs and buttons you are allowed to use.
  • Every click is sent to the server and checked there again. Changing the panel in your own game cannot unlock an action.
  • While the panel is open, the player list refreshes every 5 seconds.
  • Actions that move or heal players briefly pause the matching detections, so staff without Staff Bypass are not flagged for using them.
  • Most actions are logged to the Admin webhook channel. See Logging.
  • The panel uses the server's Language setting, English or Turkish.

Opening the Panel

With the Command

Type /cxa in the chat. The command name comes from the In-game panel row in Configuration → Staff roles & commands → Commands, so if you renamed it there, use the new name.

Console
/cxa

The header shows your server name and the roles you have, for example Owner and Admin. Press Esc to close an open dialog, and Esc again to close the panel. The × button in the top right corner closes it as well.

With a Key

You can also give the panel a key. Set Default key in Configuration → Staff roles & commands → In-game panel, for example F10. The key is stored as Config.Admin.MenuKey; leave it empty to open the panel only with the command.

The key appears in the game as CXA staff panel under Settings → Key Bindings → FiveM. Every player can change it there. FiveM remembers each player's choice, so a player who already has a binding keeps it when you change the default later.

Pick a Free Key

Every player gets the binding, not only staff. Players without a staff role who press it only see You do not have permission to use this command. Choose a key that none of your other scripts use.

Who Can Open It

  • The player must have one of the roles of the In-game panel command (cxa). The defaults are owner, admin and moderator.
  • The player must have at least one allowed action in the panel permissions table.
  • Staff Bypass alone does not open the panel. Bypass and staff roles are separate.

If one of these is missing, the chat shows You do not have permission to use this command. Typed in the server console, the command answers This command can only be used in-game.

The Players Tab

The Players tab lists everyone online with their server ID, name and ping. Frozen players are marked Frozen, staff members are marked Staff, and a coloured dot shows each player's account trust band. Your own entry is marked with "(you)".

Use the search field ("Name, ID or identifier") to filter the list. Click a player to see their details:

  • Ping, TrustScore and Status (Online or Frozen)
  • Identifiers, with a copy button next to each one. This section only appears with the Identifiers permission, and IP addresses are never shown.
  • Actions: the buttons you are allowed to use

Searching by identifier also needs the Identifiers permission, because identifiers are only sent to staff who may see them.

Actions

ButtonPermission keyDefault rolesWhat it does
SpectateSpectateowner, admin, moderatorWatch the player from their camera.
Go toGotoowner, admin, moderatorTeleports you to the player.
BringBringowner, admin, moderatorTeleports the player to you.
Freeze / UnfreezeFreezeowner, admin, moderatorFreezes the player in place, or releases them.
Revive / healReviveowner, adminRevives a dead player and restores full health.
MessageMessageowner, admin, moderatorSends the player a private chat message.
ScreenshotScreenshotowner, admin, moderatorTakes a screenshot of the player's screen.
KickKickowner, admin, moderatorRemoves the player from the server with a reason.
BanBanowner, adminBans the player for a set time or permanently.

Two more permissions control the panel itself: Players (see the player list, default owner, admin, moderator) and Identifiers (see identifiers, default owner, admin). The Bans tab uses Bans and Unban, see The Bans Tab.

Spectate, Go to, Bring, Kick and Ban are hidden when you select yourself.

Spectate

  1. Select a player and click Spectate. The panel closes.
  2. Your camera follows the player. A bar shows their name and ID with the hint BACKSPACE.
  3. Press BACKSPACE to stop, or type /cxa again. You return to the place where you started.

While you spectate, your own character is invisible, has no collision, cannot be hurt, is frozen and is kept out of sight below the player. If your game cannot find the player for more than 6 seconds, for example because they left the server, spectating stops by itself. You cannot spectate yourself.

Go To and Bring

  • Go to teleports you to the player. If you are driving a vehicle, the vehicle comes with you.
  • Bring teleports the player to your position. If they are driving, their vehicle comes with them.

Freeze

Freeze stops the player and their vehicle from moving. The player sees You were frozen by staff. in the chat. Click Unfreeze to release them; they then see You were unfrozen. A player stays frozen until you unfreeze them or they leave the server.

Revive / Heal

Revive picks the method that fits your server:

Your server runsWhat Revive does
qb-ambulancejobUses that resource's own revive, so its death state is cleared properly.
esx_ambulancejobUses that resource's own revive.
Neither of themRevives the player if they are dead, sets full health and clears blood.

If you use a different ambulance or death script, Revive uses the built-in method. Your death script may then still show its own death screen; use that script's revive instead.

Message

Message opens a dialog ("Message to John"). Type up to 200 characters and click Send. The player sees the text in their chat with the alert prefix, [CXA] by default. Line breaks are removed.

Screenshot

Click Screenshot and wait a moment ("Taking screenshot…"). The picture opens inside the panel and is also sent to the Screenshots webhook channel with your name. This needs screenshot-basic and Screenshots turned on in Configuration → System → Screenshots; otherwise the panel shows screenshot-basic is not running. Screenshots explains the settings.

Kick

Kick opens a dialog ("Kick John") with a Reason field of up to 200 characters. Click Kick to confirm. The player sees the kick screen with your reason, or No reason given if you left it empty.

Ban

Ban opens a dialog ("Ban John"):

  1. Pick a duration: Permanent, 1 day, 3 days, 1 week or 30 days. You can also type any number into Hours (0 = permanent).
  2. Type a reason of up to 200 characters.
  3. Click Ban.

The panel confirms with the new ban ID, for example John banned (CXA-7KQ2MX). The player sees the ban screen with the ban ID, the reason and the end date. The longest timed ban is 87600 hours; larger values are cut to that. Manual bans are never shared with the CXA network.

The Bans Tab

The Bans tab needs the Bans permission (default owner, admin, moderator). It lists active bans, 50 at a time, with a Load more button at the end. Use the search field ("Ban ID, name, reason or identifier") to find a ban. To search by identifier, paste the full identifier, for example discord:123456789012345678.

Click a ban to inspect it:

  • Name, ban ID and reason
  • Created, Expires and Banned by
  • Detection: what caused the ban, for example Manual or the name of a detection
  • Hardware tokens and identifiers, only with the Identifiers permission

With the Unban permission (default owner, admin), the ban details have an Unban button. The panel asks "Remove ban CXA-7KQ2MX?" and explains "The player can join again immediately." After you confirm, it shows "Ban CXA-7KQ2MX removed". If the ban was an automatic one that was shared, it is also withdrawn from the CXA network.

The same permission adds a Bulk unban button under the ban list. It removes many bans at once:

  1. Pick when the bans were issued: Last 30 min, Last hour, Last 6 hours, Last 24 hours, Last 7 days or All time.
  2. Pick a reason. The list shows every reason in that time range with the number of bans, most common first. All reasons includes every ban in the range.
  3. The panel shows how many active bans match, for example "12 active bans match this filter." Press Remove 12 bans to confirm.

Afterwards it shows "12 bans removed". Automatic bans are also withdrawn from the CXA network. A bulk unban cannot be undone, and Enter does not confirm it, so you always have to click the button.

Checks Paused During Actions

So that staff are not flagged for using the panel, some actions pause the matching detections for a short time:

ActionPaused forWhat is pausedHow long
Go toYouMovement checks15 seconds
BringThe playerMovement checks15 seconds
Freeze / UnfreezeThe playerMovement checks5 seconds
Revive / healThe playerHealth / armor modification and god mode checks10 seconds
SpectateYouEvery detectionWhile you spectate (up to 30 minutes), plus 8 seconds after you stop

Bypass & Pause Exports explains how your own scripts can do the same.

Logging

Panel actions are written to your webhooks. The webhook channels are set in Logging & Discord.

ActionWebhook channelLog title
Go to, Bring, Spectate, Freeze / Unfreeze, Revive, Message, ScreenshotAdminIn-game panel action
Screenshot (the picture itself)ScreenshotsScreenshot
KickAdminManual Kick
BanBansManual Ban
UnbanAdminBan Removed
Bulk unbanAdminBans Removed in Bulk

An In-game panel action entry names the staff member, the action and the player, for example Admin (3) -> goto -> John (12). Messages also include the text that was sent. Bans from the panel also appear in the web panel's Detections tab. Viewing the player list or browsing bans is not logged.

Setting It Up

Open Configuration → Staff roles & commands in the panel:

  • In Commands, the In-game panel row sets the command name (default cxa) and the roles that may open the panel.
  • In In-game panel, the panel permissions table sets which role may use which action, and Default key sets the optional key.

Click Save changes. Your server applies the new configuration within a minute. Staff Roles & Command Access explains roles and the permissions tables in detail.

The same permissions in config.lua:

-- Inside Config.Permissions: roles allowed to use each action of the in-game panel
Menu = {
    Players = { 'owner', 'admin', 'moderator' },     -- See the player list
    Identifiers = { 'owner', 'admin' },               -- See identifiers and hardware tokens
    Spectate = { 'owner', 'admin', 'moderator' },
    Goto = { 'owner', 'admin', 'moderator' },
    Bring = { 'owner', 'admin', 'moderator' },
    Freeze = { 'owner', 'admin', 'moderator' },
    Revive = { 'owner', 'admin' },
    Message = { 'owner', 'admin', 'moderator' },
    Screenshot = { 'owner', 'admin', 'moderator' },
    Kick = { 'owner', 'admin', 'moderator' },
    Ban = { 'owner', 'admin' },
    Bans = { 'owner', 'admin', 'moderator' },        -- Browse bans
    Unban = { 'owner', 'admin' },                     -- Remove bans
},

Recommendations

Recommended:

  • Give every role that has player actions the Players permission, because all player actions start from the list.
  • Keep Identifiers, Ban and Unban for roles you trust with personal data and permanent decisions.
  • Always write a reason when you kick or ban. It is shown to the player and saved in the logs.
  • Use Spectate before you act on a report, so you see what the player is doing.

Avoid:

  • Giving bypass to moderators only so they can teleport or spectate. The panel already pauses the right checks.
  • Choosing a Default key that another script already uses.

Staff Roles & Command Access

Bans & the CXA Network

  • Bans you create here appear in the web panel. Bans & the CXA Network explains how bans are matched and shared.

Screenshots

  • The Screenshot action uses the same settings as automatic screenshots. See Screenshots.

Console & Chat Commands

Players

  • The web panel's Players tab offers similar actions from your browser.

Limitations

  • Revive only uses the own revive of qb-ambulancejob and esx_ambulancejob. Other death scripts get the built-in revive.
  • Screenshot needs screenshot-basic and Screenshots turned on.
  • You cannot spectate, go to, bring, kick or ban yourself.
  • Each staff member can send up to 25 panel requests every 5 seconds. Requests above that are refused with Too many requests, slow down.

Common Problems

The Panel Does Not Open

What you see: You type /cxa and get You do not have permission to use this command.

How to fix it:

  • Check that one of your roles is selected for the In-game panel command in Configuration → Staff roles & commands → Commands.
  • Check that your role has at least one action in the panel permissions table.
  • Roles are cached for 30 seconds. Wait or reconnect after a change.
  • If nothing at all happens, the anticheat may not be running. Check the server console for [CXA] messages.

The Panel Opens, but the Player List Is Missing

What you see: The panel opens without the Players tab.

How to fix it:

  • Your role lacks the Players permission. Add it in the panel permissions table.

"screenshot-basic is not running."

What you see: The panel shows this message when you click Screenshot.

How to fix it:

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

"Too many requests, slow down." or "The server did not answer."

What you see: An action fails with one of these messages.

How to fix it:

  • Wait a few seconds and try again. You may send up to 25 requests every 5 seconds.
  • "The server did not answer." appears when there is no reply within 20 seconds. Check the server console for errors.

Revive Does Not Work With My Ambulance Script

What you see: The player gets health back, but their death screen stays.

How to fix it:

  • Your death script is not qb-ambulancejob or esx_ambulancejob, so the built-in revive is used. Revive the player with your death script's own command.

I Can't Stop Spectating

What you see: You are still watching the player after pressing a key.

How to fix it:

  • Press BACKSPACE, or type /cxa again.
  • If the player left, spectating stops by itself after 6 seconds and you return to your start position.

The Key Does Nothing

What you see: Pressing the key you set as Default key does not open the panel.

How to fix it:

  • Open Settings → Key Bindings → FiveM in the game and check the key next to CXA staff panel. Players who had a binding before you changed the default keep their old key.
  • Check that Default key uses a valid key name, for example F10, and that you saved.

© 2026 CodeXart Studios · CXA Anticheat