Staff Bypass

Staff bypass tells CXA Anticheat not to check a trusted person at all. Admins who use noclip, spectate, spawn vehicles or teleport as part of their work are then never warned, kicked or banned for it. You decide who gets this through four methods: txAdmin, ACE permissions, identifiers and framework groups.

Bypassed Players Skip Every Check

A bypassed player is not checked by any detection. If that account is stolen or the person misuses it, the anticheat does nothing. Only give bypass to people you would trust with full access to your server, and prefer staff roles without bypass for everyone else.

How It Works

  • A player is bypassed when any one of the four methods matches. You can use one method or combine several.
  • The result is cached for each player for CacheSeconds (60 seconds by default), so CXA does not ask ACE or your framework on every check.
  • A bypassed player skips all checks that run in their game and all server-side checks, such as explosions, entity blacklists, combat, movement and security rules.
  • Event Guard never punishes a bypassed player. If Block calls over the limit is on, event calls above the limit are still dropped.
  • Only the Identifiers method is known before a player has fully joined. Players listed there also skip Join Screening: the name filter, the ban check, the CXA network check, the duplicate account check and the VPN check.
  • In the panel's Players tab, players who currently skip checks have a staff badge next to their name.

Setting It Up

In the panel, open Configuration → Staff & Bypass → Bypass. The group says "Players matching any rule skip every check." Change the fields and click Save changes. Your server applies the new configuration within a minute.

OptionKeyDefaultWhat it does
txAdmin adminsConfig.Bypass.TxAdminAdminstruePlayers that txAdmin has recognised as admins in-game skip every check.
ACE permissionConfig.Bypass.AcePermission'cxa.bypass'Players with this ACE permission skip every check. If you don't grant it to anyone in server.cfg, the method does nothing.
IdentifiersConfig.Bypass.IdentifiersemptyPlayers with any listed identifier skip every check, including Join Screening. Up to 200 entries.
Framework groupsConfig.Bypass.FrameworkGroupsadmin, superadmin, godPlayers in one of these ESX groups or QBCore/Qbox permissions skip every check. Up to 30 entries.
Cache timeConfig.Bypass.CacheSeconds60Seconds a player's bypass result is kept before it is checked again (5 to 3600 in the panel).

The same settings in config.lua look like this. When your license is active, the values saved in the panel replace the ones in this file.

Config.Bypass = {
    TxAdminAdmins = true,                    -- Admins recognised by txAdmin skip every check
    AcePermission = 'cxa.bypass',            -- e.g. add_ace group.admin cxa.bypass allow
    Identifiers = {                          -- Any matching identifier skips every check
        'discord:123456789012345678',
    },
    FrameworkGroups = { 'admin', 'superadmin', 'god' }, -- ESX groups / QB permissions that skip checks
    CacheSeconds = 60,                       -- Bypass result cache per player
}

Check the Default Framework Groups

By default, Framework groups contains admin, superadmin and god. On ESX, QBCore and Qbox servers, everyone in these groups already skips every check. If you want your admins to be checked, remove the groups you don't fully trust.

The Four Methods

txAdmin Admins

With txAdmin admins on, players that txAdmin recognises as admins in-game skip every check. txAdmin tells CXA as soon as it recognises them, so the bypass starts right away.

Use it when your whole staff team logs in through txAdmin and everyone with a txAdmin account is fully trusted. Turn it off if you give txAdmin accounts to people who should still be checked.

ACE Permission

ACE permissions are FiveM's built-in permission system, set in server.cfg. Any player who has the ACE in ACE permission (default cxa.bypass) skips every check.

# Let one ACE group skip every check
add_ace group.headadmin cxa.bypass allow

# Put trusted people into that group
add_principal identifier.fivem:1234567 group.headadmin
add_principal identifier.discord:123456789012345678 group.headadmin

# Or give the permission to a single person directly
add_ace identifier.license:1234567890abcdef1234567890abcdef12345678 cxa.bypass allow

Create a dedicated group for bypass, like group.headadmin above, instead of reusing a large group such as group.admin. That way, giving someone admin commands does not automatically switch the anticheat off for them.

ACE Permissions Are Inherited

ACE permissions work like a tree: add_ace group.admin cxa allow grants every permission that starts with cxa., including cxa.bypass. Grant exact permissions such as cxa.role.admin instead. Never grant cxa.bypass to builtin.everyone, because that switches the anticheat off for every player.

Identifiers

An identifier is an account ID FiveM knows about a player, such as their Discord, Rockstar license or Cfx.re (FiveM) account. Add the full identifier, including its type, to Identifiers. It must match exactly.

TypeExampleWhere it comes from
discorddiscord:123456789012345678The player's Discord account, when Discord is running
licenselicense:1234567890abcdef1234567890abcdef12345678The player's Rockstar license, always present
fivemfivem:1234567The player's Cfx.re account, when they are signed in
steamsteam:110000123456789The player's Steam account, when Steam is running

You can copy a player's identifiers from the Identifiers section of the in-game panel (with the Identifiers permission) or from txAdmin.

Identifiers are the only method CXA can check while a player is still connecting. A listed player therefore also skips the connection checks, including the ban check: a banned account that is on this list can still join. Prefer license or discord, because a player cannot simply change them.

Framework Groups

Framework groups uses the staff groups of your framework:

  • ESX: the player's group must be exactly one of the listed names, for example admin.
  • QBCore and Qbox: the player must have one of the listed permissions, for example god. CXA also accepts an ACE permission with the same name.
  • Standalone servers have no framework groups, so this method does nothing there.

Your framework must start before cxa-anticheat in server.cfg, otherwise CXA cannot read the groups. On ESX and QBCore, CXA checks the group again when the framework reports that the player's character has loaded.

Which Method Should I Use?

Your situationRecommended methodWhy
A few trusted peopleIdentifiersYou see every bypassed person in one list in the panel.
A larger team with ACE groups in server.cfgACE permission on one dedicated groupYou add and remove people with one add_principal line each.
Staff ranks managed by your frameworkFramework groups, only your highest groupPromotions in your framework apply automatically.
Staff that always works through txAdmintxAdmin adminsNo extra setup; txAdmin decides who is an admin.

Whatever you choose, keep the list short. Moderators and helpers usually don't need bypass: give them a staff role instead, and the in-game panel pauses the right checks while they use its teleport, spectate and revive actions.

Bypass vs. Staff Roles

Bypass and staff roles are separate. A player can have one, the other or both.

Staff bypassStaff role
Skips anticheat checksYes, every checkNo, the player is still checked
Can use CXA commands and the in-game panelNoYes, depending on the role
Receives detection alerts in chatNoYes
Where to set itConfiguration → Staff & Bypass → BypassConfiguration → Staff roles & commands

Read Staff Roles & Command Access to set up roles.

Partial Bypass

There is no permission that skips only some detections. If a staff member should be checked but one of their tools keeps triggering a detection, use one of these instead:

  • Pause a single detection from your own script with the PauseDetection export, for example only Noclip while your admin noclip is on.
  • Pause every detection for a short time with SetTemporaryBypass, for example during a scripted cutscene.
  • Adjust the detection itself: raise its tolerance or set its punishment to log while you investigate. See Detections & Punishments.
  • Give the person a staff role without bypass. The in-game panel pauses the matching checks for its own actions.
-- Your own admin noclip command (server side)
RegisterCommand('adminnoclip', function(src)
    if not IsPlayerAceAllowed(src, 'myadmin.noclip') then -- check your own permission first
        return
    end
    exports['cxa-anticheat']:PauseDetection(src, 'Noclip', 600) -- only Noclip is paused, for 10 minutes
    TriggerClientEvent('myadmin:toggleNoclip', src)             -- your script's own noclip event
end, false)

Always check permissions on the server before you call these exports. If any player could trigger the pause, cheaters could use it too. Bypass & Pause Exports lists every key you can pause.

Caching and Refreshing

  • Server-side checks re-check the bypass after CacheSeconds (60 seconds by default).
  • Checks running in the player's game learn the bypass state when the player finishes loading, when ESX or QBCore reports the character as loaded, when txAdmin recognises an admin, and when a script calls RefreshBypass.
  • If you give someone bypass while they are online, ask them to reconnect, or call RefreshBypass from your script.
-- After your script changed a player's group or ACE
exports['cxa-anticheat']:RefreshBypass(src)                  -- re-checks right away and tells the player's game

local bypassed = exports['cxa-anticheat']:IsPlayerBypassed(src) -- true if the player skips every check

Recommendations

Recommended:

  • Keep bypass for the owner and a few senior admins.
  • Use a dedicated ACE group such as group.headadmin for bypass.
  • Review Framework groups after setup, because admin, superadmin and god are bypassed by default.
  • Use license or discord identifiers in the Identifiers list.

Avoid:

  • Giving bypass to moderators just because one tool triggers a detection. Pause that detection instead.
  • Granting cxa as a whole with add_ace, because that includes cxa.bypass.
  • Leaving former staff in the Identifiers list. They keep skipping every check, including the ban check.

Staff Roles & Command Access

  • Staff Roles & Command Access decides who can use commands and the in-game panel.
  • Roles do not skip checks; combine them with bypass only for people who need both.

In-Game Panel (/cxa)

  • The in-game panel pauses the matching checks for goto, bring, spectate, freeze and revive.
  • Staff without bypass can use it safely.

Bypass & Pause Exports

  • Bypass & Pause Exports covers IsPlayerBypassed, RefreshBypass, SetTemporaryBypass, PauseDetection and AllowTeleport.

Join Screening

  • Players in the Identifiers list skip the checks in Join Screening.
  • ACE, framework group and txAdmin bypass only start after the player has joined.

Limitations

  • There is no per-detection bypass permission. Use the pause exports or adjust the detection instead.
  • Only the Identifiers method works while a player is connecting.
  • Framework groups need ESX, QBCore or Qbox, and the framework must start before CXA.
  • A bypass given to an online player reaches the checks in their game only after a reconnect or RefreshBypass.

Common Problems

My Admin Still Gets Kicked or Banned

What you see: A staff member who should be bypassed is still punished by a detection.

How to fix it:

  • Open the Players tab and check whether the player has a staff badge. If not, none of the four methods matches.
  • For Identifiers, compare the entry character by character with the player's real identifier, including the type prefix such as discord:.
  • For ACE, check that the add_ace and add_principal lines are in server.cfg and that the identifier in add_principal is the player's.
  • For framework groups, check the exact group name and that your framework starts before cxa-anticheat.
  • Ask the player to reconnect so the checks in their game learn the new state.

Every Admin Skips the Anticheat, but I Never Added Anyone

What you see: Your admins are never flagged, even when you test detections on purpose.

How to fix it:

  • Framework groups contains admin, superadmin and god by default. Remove the groups you want checked.
  • txAdmin admins is on by default. Turn it off if your txAdmin admins should be checked.
  • Look for add_ace lines in server.cfg that grant cxa.bypass or the whole cxa permission.

A Banned Player Can Still Join

What you see: A ban exists, but the player connects without being stopped.

How to fix it:

  • Check whether one of the player's identifiers is in the Identifiers list. Listed players skip the ban check while connecting.
  • Remove the entry, save, and the next connection is checked again.

My Changes Do Not Apply

What you see: You changed the bypass settings, but nothing changes in-game.

How to fix it:

  • Make sure you clicked Save changes. The server applies a saved configuration within a minute.
  • Wait for the cache time (CacheSeconds) to pass, or ask the player to reconnect.

© 2026 CodeXart Studios · CXA Anticheat