Remote Actions

Remote actions let you run anticheat commands on your server from the browser, without opening the server console: add or remove Event Guard, reload the ban list, pull the latest configuration, unban by ban ID and send a message to every player. Player actions such as kick and ban work the same way. Your server picks each action up on its next sync with the panel.

Your Server Must Be Online

Actions are delivered when your server syncs with the panel. While the server is offline, an action waits in the queue and runs once the server is back.

How It Works

  1. You press Run (or Send, Unban, Ban) in the panel. The action is queued with the status pending.
  2. Your server syncs with the panel about every 15 seconds and takes up to 20 waiting actions. Their status changes to sent.
  3. The anticheat runs each action as if it was typed in the server console.
  4. The result is reported with the next sync and the status changes to done or failed.

An action usually finishes within 30 seconds. Give it up to a minute on a busy server. Every action is also written to the activity log with your name. Bans, unbans, screenshots and Event Guard changes from the panel are also logged in Discord, with Panel: <your name> as the admin.

Server Commands

Open your license and go to Commands. The Server commands card lists everything you can run on the server.

Command in the panelConsole equivalentWhat it doesWho can run it
Inject Event GuardcxainjectAdds the Event Guard line to the fxmanifest.lua of every resource with server scripts that does not have it yet.Owner, admin
Remove Event GuardcxauninjectRemoves the Event Guard line from every fxmanifest.lua again.Owner, admin
Reload banscxareloadReloads the ban list from the database into memory.Owner, admin, editor
Sync configurationcxasyncMakes the server pull the latest configuration now instead of at the next sync.Owner, admin
Unban by ban IDcxaunban <banId>Removes a ban. Automatic bans are also withdrawn from the CXA network.Owner, admin, editor
Bulk unbannoneRemoves every active ban issued in a time range, optionally only those with a given reason or detection.Owner, admin, editor
Message to everyonenoneShows a message (up to 200 characters) in the chat of every online player.Owner, admin, editor

Inject Event Guard

Event Guard limits how often each player can call the server events of your resources. Inject asks for confirmation, then edits the fxmanifest.lua files of your resources. The result shows a summary such as:

Output
Event Guard injected into 42 resource(s), 3 already had it, 12 skipped, 0 failed.

Restart the server afterwards, because a resource only loads Event Guard when it starts. See Event Guard.

Remove Event Guard

Remove Event Guard is marked in red because it takes protection away. After the next restart, the server events of your resources are no longer rate limited (no longer limited in how often a player can call them).

Reload bans

Active bans live in memory so joins never wait for the database. Run Reload bans after you added, edited or deleted bans directly in the cxa_bans table. The result shows Ban list reloaded, 12 active bans. with your own number.

Sync configuration

Saved configurations reach your server within a minute anyway. Sync configuration only skips the wait. With SvConfig.License.AutoReload = true (default), the anticheat reloads itself 5 seconds after it receives a new configuration. With AutoReload = false, the new configuration is downloaded but only used after a restart.

Unban by ban ID

Enter the ban ID exactly as it appears on the ban screen or in the ban log, for example CXA-7KQ2MX, and press Unban. The result shows the ban ID when it worked, or ban_not_found. See Bans & the CXA Network.

Bulk unban

Use Bulk unban to undo a wave of bans at once, for example after a detection fired by mistake.

  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. To remove only some of them, type a reason or a detection name, for example Silent Aim. Every ban whose reason or detection contains that text is included, and capital letters do not matter. Leave the field empty to include every reason.
  3. Press Remove bans. The panel tells you exactly what will be removed and asks you to confirm.

The result shows how many bans were removed, for example 12 bans removed. Automatic bans are also withdrawn from the CXA network, and the Admin webhook channel gets one Bans Removed in Bulk entry with the filter you used.

This Cannot Be Undone

All time with an empty reason removes every active ban on your server. A bulk unban cannot be undone.

Message to everyone

Type the message and press Send. Every online player sees it in their chat with your alert prefix, [CXA] by default.

Player Actions

On the Players page and the Live map tab, staff can also act on a single online player. Each action goes through the same queue.

ActionWhat happens on the serverResult
MessageSends a chat message to this player only.sent
ScreenshotTakes a screenshot and posts it to the Screenshots channel. Needs screenshot-basic.sent_to_webhook
KickDrops the player with your reason.The player's name or kicked
BanBans the player for the hours you set (0 = permanent) and drops them.The new ban ID

All player actions need the moderate permission (owner, admin or editor). The last ten actions are listed under Recent panel actions on the Players page. See Players.

Results and Statuses

The Results card on the Commands tab shows the last commands sent from this panel, with the status, the result text, who sent it and when. While a command is waiting, the card refreshes every few seconds.

StatusMeaning
pendingQueued, waiting for the server's next sync.
sentDelivered to the server, waiting for the result.
doneThe server ran the action. The result text says what happened.
failedThe action did not work. The result text says why.

Common results of failed actions:

ResultMeaning
player_offlineThe player left before the action arrived.
ban_not_foundNo active ban has this ID.
screenshot_unavailableScreenshots are turned off or screenshot-basic is not started.
screenshot_failedThe player's game did not send a screenshot in time.
No answer from the serverThe server received the action but did not report back within 5 minutes.

Who Can Use Remote Actions

The Commands tab is only shown to members whose team role has the moderate permission: owner, admin and editor. Inject Event Guard, Remove Event Guard and Sync configuration also need manageServer, so editors see them greyed out. Viewers can't run any action. See Team Access.

Remote actions use your panel role. The in-game staff roles from Configuration → Staff roles & commands decide who may use the commands in the game and the console, not in the panel.

Remote Actions and Console Commands

Every server command in the panel does the same as its console command. The Command reference card on the Commands tab lists all console and chat commands with the names you configured, and shows whether each one can be used from the Console and In-game, and by which roles. Inject and Uninject are Console only in the game, but you can run them from the panel. Change names and access in Configuration → Staff roles & commands. See Console & Chat Commands.

Limits

  • Up to 60 actions per minute per member.
  • Up to 50 waiting actions per license.
  • Messages and reasons up to 200 characters.

Recommendations

Recommended:

  • Run Inject Event Guard once after installing new resources, then restart the server.
  • Use Reload bans after every manual change in the cxa_bans table.
  • Copy ban IDs from the ban log when you unban, so they are spelled exactly right.
  • Check the Results card before you send the same action again.

Avoid:

  • Sending the same command several times while the first one is still pending. Every copy runs.
  • Running Remove Event Guard to fix a single false positive. Add the event to Ignored events instead, see Event Guard.
  • Giving the editor role to people who should not ban, unban or message players.

Event Guard

  • Inject Event Guard and Remove Event Guard run the same code as cxainject and cxauninject.
  • See Event Guard.

Bans & the CXA Network

Config Editor

  • A saved configuration reaches the server within a minute. Sync configuration only makes it faster.
  • See Config Editor.

Team Access

  • The team role decides which actions a member can run.
  • See Team Access.

Common Problems

An Action Stays "pending"

What you see: The status does not change from pending.

How to fix it:

  • Check that the server is online in Overview. Offline servers pick up the action when they are back.
  • Make sure the anticheat is running and the license is active.

"No answer from the server"

What you see: An action changes to failed with No answer from the server.

How to fix it:

  • The server received the action, but the anticheat was not active or restarted before it could answer. Check the console for [CXA] warnings.
  • Send the action again once the server is running normally.

The Run Button Is Greyed Out

What you see: You can see the Commands tab, but some buttons can't be pressed.

How to fix it:

  • Inject Event Guard, Remove Event Guard and Sync configuration need the owner or admin role.
  • Unban needs a ban ID of at least 3 characters, and Send needs a message.

"Too many attempts, try again later."

What you see: The panel refuses a new action with Too many attempts, try again later. or Something went wrong, please try again.

How to fix it:

  • If you sent more than 60 actions in a minute, wait a minute and try again.
  • The license may have 50 waiting actions. Wait until the server has taken them.

Sync Ran but the Server Uses the Old Configuration

What you see: Sync configuration is done, but settings did not change.

How to fix it:

  • Make sure you pressed Save changes in Configuration first.
  • If SvConfig.License.AutoReload is false, restart the anticheat to use the new configuration.

© 2026 CodeXart Studios · CXA Anticheat