Detections & Punishments

A detection is a single check that looks for one kind of cheat, for example noclip, a blacklisted weapon or an invisible explosion. Every detection has its own switch and its own punishment, so you decide per check whether CXA only writes a log or removes the player. This page explains where the checks run, what each punishment does and how to switch them on safely.

Avoid False Positives on a New Server

Some detections can clash with your own scripts, for example a hospital script that heals players above the normal maximum. Set those detections to log for the first days, read the logs, then raise the punishment. See Recommended Rollout.

How It Works

  1. A check notices something suspicious, for example a player hovering high above the ground.
  2. If the detection has a Tolerance, the check must fail several times in a row before anything happens.
  3. A client check then sends a report to your server. A server check decides on the server directly.
  4. The server skips the player if they are bypassed (trusted staff) or if a script paused this detection for them.
  5. The server applies the detection's punishment: ban, kick, warn, log or none.
  6. For every punishment except none, the detection is written to the server console, the panel's Detections tab and your Discord webhook, and online staff get a chat alert. Each of these outputs can be switched off in Configuration → Logs.

Client and Server Detections

CXA runs checks in two places. Both matter, because they see different things.

Client Detections

Client detections run inside each player's game. They can see things only the game knows, such as whether the player's collision is turned off, which weapons the player holds or whether a cheat menu has hooked a function. They cost only the player's FPS. Your server receives a message only when a check finds something.

  • They start StartDelay seconds after a player joins (15 by default), so loading screens are not checked.
  • Each check runs every Interval milliseconds.
  • A client reports the same detection at most once every ReportCooldown seconds (10 by default).
  • The server accepts at most MaxReports reports per player within Window seconds (20 within 10 by default) and ignores the rest, so fake reports cannot flood your server.

Because these checks run on the player's computer, a cheat could try to stop them. CXA watches for that too: the Heartbeat notices when the anticheat stops answering, Blocked anticheat UI (NuiBlock) notices a blocked anticheat page, Lua injection (Injection) notices hooked functions and Resource stop (ResourceStop) notices resources a player stopped in their game.

Server Detections

Server detections run on your server. They read what players' games send to the server: entities being created, explosions, damage, weapon events and server events. A player has no access to code that runs on your server, so a cheat cannot switch these checks off or change what they decide. The panel describes them as "impossible to bypass from the client".

Most server detections react to an event and have no Interval. Two of them scan on a timer instead: Server movement check (Movement) and Objects attached to players (AttachedObjects).

Checks That Use Both Sides

Some detections collect data in the player's game and let the server make the final decision, so a single player cannot fake the result.

DetectionIn the player's gameOn the server
Shooting through walls (MagicBullet)Victims report hits from shooters they could not seeActs only when 3 different victims report the same shooter within 300 seconds
Vehicle ram (AntiRam)Looks for fast driverless vehicles near the playerConfirms the vehicle is driverless and fast, deletes it and punishes the player whose game created it
Resource injection (ResourceInjection)Reports every resource that starts in the game, and rescans the full resource list every RescanInterval seconds (15 by default) to catch executors that hide the start eventPunishes only if your server does not have a resource with that name
Resource stop (ResourceStop)Reports a resource that stopped in the gameWaits 10 seconds and ignores resources your server stopped or restarted itself
Game data scan and Animation timingRead weapon and vehicle values, measure reloads and running speedCompare the values with the other players on your server, see Modified Game Files

Every detection, its key and its default punishment are listed in All Detections.

Punishments

Every detection has a Punishment. The panel shows it as a dropdown with these options:

ValuePanel labelWhat happensDiscord channel
banBanCreates a ban with an ID like CXA-7KQ2MX, removes the player with the ban screen, logs it and alerts staffBans
kickKickRemoves the player with the kick screen, logs it and alerts staffKicks
warnWarn (player stays)Shows the player an on-screen warning, logs it and alerts staff. The player stays on the serverWarns
logLog onlyLogs it and alerts staff. Nothing happens to the playerThe detection's LogChannel, Detections by default
noneBlock silentlyWrites no log and sends no alertNone

Good to know about each punishment:

  • none does not undo what a check blocks by itself. A cancelled explosion stays cancelled and a removed weapon stays removed. For a check that only watches, such as Noclip, none means nothing happens at all, so switching the detection off is clearer.
  • Once a ban or kick starts, CXA ignores further detections from that player and cancels their explosions and entity spawns until they are gone.
  • Automatic bans from the detections in Shared detections are sent to the CXA network when Share my automatic bans is on. Manual bans are never shared. See Bans & the CXA Network.
  • warn does not count up by itself. A player can be warned again and again without being kicked; the text only tells them they will be removed. Use kick when repeated cheating must have a consequence.

The Warning Players See

With warn, the player sees a banner at the top of the screen for about 9 seconds, hears a short sound and gets the same text in chat after your alert prefix:

Output
Anticheat warning
Anticheat warning: Noclip. Keep doing it and you will be removed from the server.

The text follows the language set in Configuration → General → Language. With Turkish, the same warning reads Anticheat uyarısı: Yasadışı noclip kullanımı. Devam edersen sunucudan atılırsın.

Detection Settings

Most detections share the same settings. The panel only shows the ones that apply to a detection.

OptionKeyExample defaultWhat it does
Enabled (the switch on each detection)EnabledtrueTurns the detection on or off
PunishmentPunishmentbanWhat happens when it triggers, see Punishments
Ban durationBanDuration0Hours the ban lasts, 0 = permanent. Only used with ban
ToleranceTolerance6 (Noclip)Failed checks in a row before CXA acts
Check intervalInterval500 (Noclip)How often a client check runs, in milliseconds
ScreenshotScreenshotfalseAttaches a screenshot of the player's screen to the Discord log
Log channelLogChannelDetectionsDiscord channel used when the punishment is log

Ban Duration

BanDuration is in hours: 0 means permanent, 72 means three days. The panel accepts up to 87600 hours. If a detection has no BanDuration, CXA uses Default duration from Configuration → Ban system (Config.Ban.DefaultDuration, 0 by default).

Tolerance

Tolerance is the number of failed checks in a row before CXA acts. One normal result resets the count. A higher value means fewer false positives and a slightly later reaction. Noclip, for example, runs every 500 ms with a Tolerance of 6, so a player has to hover for about three seconds before it triggers.

A few detections count events within a time window instead of in a row. Wall shot counts hits through walls within Window seconds, No fall damage counts falls within 10 minutes, and Vehicle jump, Horn boost and Teleport to waypoint count within one minute. The comment next to each key in config.lua says which kind a detection uses.

Check Interval

Interval sets how often a client check runs, in milliseconds. A lower value reacts faster and costs the player a little more FPS. It never costs server performance, because the server only receives reports. The client loop itself ticks every Scheduler tick (Config.Client.SchedulerTick, 100 ms by default), so an interval below that runs at the tick rate. The Heartbeat is the exception: its Interval is in seconds.

Screenshot

Screenshot = true takes a screenshot of the player's screen and attaches it to the Discord log. It needs the screenshot-basic resource and Configuration → System → Screenshots switched on. With ban or kick, CXA waits for the screenshot before it removes the player, at most Timeout (Config.Screenshot.Timeout, 6000 ms), and then punishes without one. See Screenshots.

Log Channel

LogChannel picks the Discord channel for log results. Bans, kicks and warnings always go to the Bans, Kicks and Warns channels. The available channels are Detections, Bans, Kicks, Warns, Explosions, Entities, Connections, DevTools, Chat and Admin. If a channel has no webhook, CXA uses your Default webhook. You set the webhook URLs in the panel under Webhooks & keys, see Logging & Discord.

By default, explosions log to Explosions, Entity blacklist and Entity spam to Entities, the chat filter to Chat, NUI devtools to DevTools and everything else to Detections.

Admin Alerts and Cooldowns

When a detection triggers with any punishment except none, every online staff member gets a red chat line like this:

Output
[CXA] John (ID: 12) flagged for Noclip [ban]

Staff means players with one of the roles from Staff Roles & Command Access or with the ACE permission (FiveM's built-in permission system) cxa.admin. The flagged player never gets an alert about themselves.

Cooldowns keep alerts and logs readable when the same check fires many times:

OptionWhere in the panelKeyDefaultWhat it does
In-game alertsStaff & Bypass → AdminConfig.Admin.InGameAlertstrueTurns staff chat alerts on or off
Alert cooldownStaff & Bypass → AdminConfig.Admin.AlertCooldown10 sMinimum time between two alerts for the same player and detection
Alert prefixStaff & Bypass → AdminConfig.Admin.AlertPrefix[CXA]Chat prefix of alerts and player warnings
Detection cooldownLogs → LoggingConfig.Logs.DetectionCooldown10 sRepeated log and warn results for the same player and detection within this time are skipped completely, with no log and no alert
Report cooldownSystem → ClientConfig.Client.ReportCooldown10 sA client reports the same detection at most once in this time

Bans and kicks are never skipped by a cooldown.

Heartbeat

The heartbeat tells your server that the anticheat is still running in a player's game. The game sends a small signal every few seconds. If the server hears nothing for too long, it applies the heartbeat's punishment with the reason Anticheat heartbeat lost. This catches cheats that stop or freeze the anticheat script.

OptionKeyDefaultWhat it does
PunishmentConfig.ClientDetections.Heartbeat.PunishmentkickWhat happens when the heartbeat is lost
IntervalInterval15 sSeconds between two heartbeats. Unlike other client checks, this one is in seconds
TimeoutTimeout90 sSeconds without a heartbeat before the punishment
First heartbeat timeoutFirstTimeout600 sTime a player has after joining to send the first heartbeat, so long loading screens are not punished

The server looks at all heartbeats every 10 seconds. You find these settings under Configuration → Client detections → Heartbeat.

Keep the Heartbeat on kick

A lost heartbeat can also come from a game that froze or a connection that dropped for a long time. kick removes the player without a ban, so an honest player can simply reconnect.

[PERF] Markers

Some settings carry a [PERF] note in config.lua and an amber PERF badge in the panel. According to the note in config.lua, they can raise your server's resmon values (FiveM's resource monitor) or cause hitch warnings on high-population servers (150+ players). Read the note before you turn one on or lower its interval.

SettingWhy it is marked
God mode (server heuristic) (GodModeHeuristic)Starts one short timer for every damaging hit on a player
Server movement check (Movement)Reads every player's position; keep Players per tick low on big servers
Objects attached to players (AttachedObjects)Scans every networked object and vehicle each Interval
Cleanup on detection (EntitySpam.CleanupOnDetection)Loops over every server entity once to delete the spammer's entities
Screenshots (Config.Screenshot.Enabled)The server decodes and uploads every screenshot

More settings with this marker, and how to tune them, are on Performance Tuning.

Bypass and Pauses

There are two ways to stop CXA from checking a player.

Bypass

Players who match Config.Bypass (logged-in txAdmin admins, the cxa.bypass ACE permission, listed identifiers or framework groups) skip every check, on the client and on the server. The result is cached for CacheSeconds (60 by default). There is no bypass for single detections. See Staff Bypass.

Pauses

Your own scripts can pause one detection for one player for a few seconds with the PauseDetection export. While a pause runs, the server ignores that detection and the player's game stops running that check. SetTemporaryBypass pauses every detection, AllowTeleport pauses Movement (5 seconds by default). Pauses end by themselves. See Bypass & Pause Exports.

-- Inside your own resource, on the server side
exports['cxa-anticheat']:PauseDetection(source, 'FastVehicleExit', 5) -- your script pulls the player out of a vehicle
exports['cxa-anticheat']:AllowTeleport(source, 5)                     -- your script teleports the player

The in-game panel pauses checks by itself: Goto pauses Movement for the staff member for 15 seconds, Bring and Freeze pause it for the target for 15 and 5 seconds, and spectating pauses every check for the staff member until they stop.

Blocking Is Not a Punishment

Bypass and pauses stop punishments. A few protections block something without punishing, and they keep working: Event Guard still drops calls above the limit for bypassed staff, and the entity blacklist still cancels a blacklisted model for a paused player. Bypassed players can spawn blacklisted entities.

Setting It Up

  1. Sign in on the panel and open your license.
  2. Open Configuration.
  3. Choose Client detections or Server detections. The checks for modified game files have their own section, Game files (RPF).
  4. Turn a detection on with its switch, choose a Punishment and adjust its values. The search box (Search settings) finds a detection by name, for example noclip.
  5. Click Save changes. Your server picks up the new configuration within a minute and reloads the anticheat.

When the new configuration arrives, the server console prints:

Output
[CXA] New configuration received from the panel, reloading the anticheat in 5 seconds.

Config Editor explains the editor itself, and Config with an AI Assistant helps you set the detections for your own scripts.

Every server runs different scripts, so no configuration fits all servers. This rollout catches cheaters from the first day and keeps honest players safe while you learn how your scripts behave.

Step 1 — Start Risky Detections on log

Set the detections that often clash with scripts to log (or keep them on log) for the first days. The reasons below come from the notes in config.lua.

DetectionDefaultWhy it can clash with scripts
Health / armor (HealthArmor)banYour server uses a custom maximum health
Damage modifier (DamageModifier)banOne of your scripts boosts weapon damage
Blacklisted weapons (BlacklistedWeapons)banA shop or job hands out a weapon from the list
Blacklisted commands (BlacklistedCommands)banOne of your resources registers a command with a listed name
One punch (OnePunch)banA fight script boosts melee damage
Infinite stamina (InfiniteStamina)kickYour server gives infinite stamina on purpose
Instant vehicle exit (FastVehicleExit)kickA script pulls players out of vehicles
Server event abuse (Event Guard)kickA script calls one of its own events many times by design
God mode (GodMode)log, offSome frameworks make players invincible during character selection
No ragdoll (NoRagdoll)log, offSome scripts turn off ragdoll on purpose
Infinite ammo (InfiniteAmmo)logYour server gives infinite ammo on purpose
Plate changer (PlateChange)logA fake plate script changes plates
Vehicle god mode (VehicleGodMode)logYour scripts make some vehicles bulletproof
Voice range (VoiceRange)logA megaphone script uses a larger range
God mode (server heuristic) (GodModeHeuristic)logFriendly fire is turned off on your server
Invisible entities (InvisibleEntity)logScripts spawn hidden props
Explosion typesBlock + logHeists, ATM robberies and fireworks create explosions, see Explosion Control

Step 2 — Watch the Logs

Play normally for a few days and read the panel's Detections tab and your Discord channels. A detection that fires for many different players at the same place or during the same activity is almost always a script, not a cheater. Find the script and note which detection it triggers.

Step 3 — Fix the Cause, Then Raise the Punishment

For each false positive, fix the cause first:

  • Raise the threshold, for example Max health for a custom health system.
  • Add the item to the detection's ignore list, for example Ignored vehicles for bulletproof job cars.
  • Let the script pause the detection with PauseDetection while it does its job.
  • Turn the detection off if your server allows that behavior on purpose.

When a detection stays clean, move it to warn or kick, and to ban once you trust it. The detections in Shared detections (Configuration → Network & trust → Global bans) are the ones CXA treats as high-confidence, so they are good candidates for ban from the start.

Recommendations

Recommended:

  • Raise Tolerance before you lower a punishment. Many false positives disappear with two or three more checks in a row.
  • Give staff access through Staff Bypass instead of turning detections off.
  • Let your scripts call PauseDetection when they teleport, heal or warp players.
  • Turn on Screenshot for detections you ban on, so you can review bans later.

Avoid:

  • Setting every detection to ban on the first day.
  • Using none to hide a noisy detection. Fix the cause or turn it off, so you still know what is going on.
  • Lowering client intervals far below the defaults. Faster checks rarely catch more, they only cost players FPS.

Staff Bypass

  • Bypassed staff skip every check, so they never trigger detections.
  • Pauses from scripts are per detection and per player, bypass is for everything.
  • See Staff Bypass.

Server Exports

  • PauseDetection, SetTemporaryBypass and AllowTeleport pause checks from your scripts.
  • FlagPlayer lets your own scripts report a player with any punishment, logged as External.
  • See Bypass & Pause Exports and Custom Flags & Trust.

Logging & Discord

  • Every punishment except none appears in the panel's Detections tab.
  • Each punishment has its own Discord channel, log uses the detection's LogChannel.
  • See Logging & Discord.

Rule Engine

  • Your own rules can block, log, warn, kick or ban on top of the detections.
  • Rules are logged as SecurityRule.
  • See Rule Engine.

Common Problems

An Honest Player Was Banned

What you see: A player who did not cheat was banned by a detection.

How to fix it:

  • Remove the ban with cxaunban <banId>, for example cxaunban CXA-7KQ2MX, or with Unban on the player in the panel's Players tab.
  • Open the panel's Detections tab and check which detection banned the player and what the details say.
  • Set that detection to log and raise its Tolerance or threshold, then follow the Recommended Rollout.
  • If a script caused it, let the script call PauseDetection for that detection.

My Staff Get Detected

What you see: Admins using noclip, spectate or teleport from an admin menu get logged or kicked.

How to fix it:

  • Add them to the bypass: ACE permission cxa.bypass, their identifiers, or their framework group. See Staff Bypass.
  • The staff member should rejoin after you change the bypass, so their game picks up the new state. Scripts can call the RefreshBypass export instead.
  • Staff roles alone do not bypass checks. Roles give access to commands and alerts, bypass skips the checks.

Staff Get No Alerts in Chat

What you see: Detections appear in the logs, but nobody gets a chat alert in game.

How to fix it:

  • Check that In-game alerts is on in Configuration → Staff & Bypass → Admin.
  • Check that the staff member has a staff role or the cxa.admin ACE permission.
  • The same player and detection only alert once every Alert cooldown (10 seconds).
  • Detections with none never alert.

A Detection Is Logged Only Once Every Few Seconds

What you see: A player triggers a log detection many times, but only some of the hits appear.

How to fix it:

  • This is Detection cooldown (10 seconds by default) in Configuration → Logs. It skips repeated log and warn results of the same player and detection.
  • Lower it if you need every single hit, or set it to 0.

Players Get Kicked With "Anticheat heartbeat lost"

What you see: Players are kicked and the log shows Anticheat heartbeat lost.

How to fix it:

  • Look at the details: lastHeartbeat: never means the first heartbeat never arrived, a time like 95s ago means it stopped later.
  • If honest players with slow computers are affected, raise First heartbeat timeout or Timeout in Configuration → Client detections → Heartbeat.
  • If one player is affected again and again while others are fine, watch that player. Cheats that stop the anticheat cause exactly this.

Screenshots Are Missing From the Logs

What you see: Screenshot is on for a detection, but the Discord log has no image.

How to fix it:

  • Turn on Configuration → System → Screenshots. The per-detection switch alone is not enough.
  • Make sure screenshot-basic is running (ensure screenshot-basic in server.cfg).
  • Screenshots only appear in Discord logs, not in the panel's Detections tab.

© 2026 CodeXart Studios · CXA Anticheat