Network Convars

Convars are FiveM's server settings, the set ... lines you know from server.cfg. CXA sets six of them every time it starts, to close gaps that mod menus use: ScriptHookV trainers, taking over other players' entities, networked sounds, phone explosions and state bag spam.

Applied When CXA Starts

CXA writes these values once your license is verified and the configuration has loaded, a few seconds after the server starts. It writes them again after every reload, for example when you save a new config. They replace the same lines in server.cfg.

How It Works

  • When the anticheat starts, CXA reads Config.Network and sets one FiveM convar per option.
  • An option that is switched off is left alone. CXA does not set the convar back to FiveM's value; it simply stops touching it. Whatever value it had stays until the whole server restarts.
  • Request control filter is only written when it is a whole number from 0 to 4. The state bag limits are only written when State bag rate limit is above 0.
  • With Debug mode on (Config.Debug = true), the console confirms each value, for example [CXA-DEBUG] Convar sv_filterRequestControl set to 2.

Setting It Up

Open Configuration → Network & rules → Network hardening in the web panel. The group has no on/off switch; each option works on its own.

OptionKeyDefaultFiveM convarWhat it does
Block ScriptHookVBlockScriptHooktruesv_scriptHookAllowedKeeps ScriptHookV trainers off your server.
Request control filterFilterRequestControl2sv_filterRequestControlFilters requests to take control of other players' entities. 0 = off, 4 = strictest.
Disable networked soundsDisableNetworkedSoundstruesv_enableNetworkedSoundsStops game sounds that one player can play for everyone.
Disable phone explosionsDisablePhoneExplosionstruesv_enableNetworkedPhoneExplosionsStops networked phone explosions.
State bag rate limitStateBagRateLimit75rateLimiter_stateBag_rateState bag updates per second per player. 0 = FiveM default.
State bag burstStateBagBurst125rateLimiter_stateBag_burstShort spikes of state bag updates allowed per player.

The same defaults in config.lua. With a license, the values you save in the panel replace them.

Config.Network = {
    BlockScriptHook = true,                  -- Keeps sv_scriptHookAllowed off, ScriptHookV (.asi trainers like Menyoo) cannot join
    FilterRequestControl = 2,                -- 0 = off, 1-4 = stricter, blocks taking control of other players' entities (vehicle hijack)
    DisableNetworkedSounds = true,           -- Stops networked sounds that cheats use for ear rape
    DisablePhoneExplosions = true,           -- Stops networked phone explosions
    StateBagRateLimit = 75,                  -- State bag updates per second per player, 0 = FiveM default
    StateBagBurst = 125,
}

The Convars in Detail

Block ScriptHookV

ScriptHookV is a single-player modding tool for GTA V. It loads .asi plugins, for example trainers like Menyoo, that can spawn items, teleport and change the game freely. FiveM only lets players with ScriptHookV join when sv_scriptHookAllowed is on.

  • What CXA sets: sv_scriptHookAllowed to false.
  • CXA default: on (BlockScriptHook = true).
  • When to change it: only on a private test server where you want trainers on purpose. A public server should keep it on.

If the convar was on when CXA started, for example because server.cfg contains sv_scriptHookAllowed 1, the console shows this yellow warning:

Output
[CXA] sv_scriptHookAllowed was on, ScriptHookV mod menus could join. CXA turned it off, also remove it from server.cfg.

CXA has already switched it off at that point. Remove or change the line in server.cfg as the warning says, so your config matches what really runs.

Request Control Filter

With OneSync, every networked entity (a vehicle, a ped or an object that all players see) is run by one player's game, called its owner. When another player's game wants to move or change that entity, it sends a request for control. Normal gameplay does this all the time, for example when you get into a car someone else just left. Mod menus abuse it to take over vehicles under other players, throw them around or delete them.

sv_filterRequestControl tells FiveM which of these requests to refuse. CXA writes your number unchanged:

ValueEffect
0Off. FiveM accepts every control request.
1Filtering on, the least strict level.
2CXA default and the value the panel recommends.
3Stricter than 2.
4The strictest level.
  • What CXA sets: sv_filterRequestControl to your value, only when it is a whole number from 0 to 4.
  • CXA default: 2.
  • When to change it: if a script that moves vehicles or peds owned by other players stops working after you install CXA, for example towing, carrying or putting someone into a car, lower the value one step at a time and test again. Raise it only after testing your scripts on a stricter level.

Networked Sounds

GTA V can play a sound on every nearby player's game when one player's game asks for it. Cheat menus use these networked sounds to blast loud noise at everyone.

  • What CXA sets: sv_enableNetworkedSounds to false.
  • CXA default: on (DisableNetworkedSounds = true).
  • When to change it: if one of your scripts plays game sounds for other players through the game itself and they are no longer heard. Sound resources that play their own audio files through server events are not affected by this convar; CXA watches those events with the Sound abuse detection instead.

Phone Explosions

GTA V has a networked event that makes a phone explode. Cheats use it to cause explosions at other players.

  • What CXA sets: sv_enableNetworkedPhoneExplosions to false.
  • CXA default: on (DisablePhoneExplosions = true).
  • When to change it: only if one of your scripts relies on phone explosions.

State Bag Limits

State bags are small pieces of data that FiveM keeps in sync between the server and every player, attached to a player, an entity or the whole server. Scripts use them for things like job status, HUD values or voice settings, for example through LocalPlayer.state. Every change a player's game makes is sent over the network, so a cheat that floods state bag updates can lag the server and other players.

  • What CXA sets: rateLimiter_stateBag_rate to State bag rate limit (updates per second per player) and rateLimiter_stateBag_burst to State bag burst (how many updates may arrive in one short spike). Decimals are cut off.
  • CXA default: 75 per second with a burst of 125. Panel ranges: 0 to 1000 for the rate, 0 to 2000 for the burst.
  • With State bag rate limit at 0, CXA does not touch either convar and FiveM's own limits apply.
  • When to change it: if the console shows rate limit messages about state bags for normal players, or a script that syncs data through state bags starts lagging or losing updates, raise both values and test again.

Keep the Burst Above the Rate

CXA writes State bag burst exactly as you set it, including 0. A burst lower than the rate can cut off normal updates. If you are unsure, keep the burst at least as high as the rate.

Putting Them in server.cfg

You don't need these lines, because CXA sets the values itself. If you want the same values from the very first second after a start, before the license is verified, you can also put them in server.cfg. Use the values you set in the panel.

# Same values as the CXA defaults (optional, CXA sets them anyway)

# No ScriptHookV trainers
set sv_scriptHookAllowed false

# Filter control requests for other players' entities
set sv_filterRequestControl 2

# No networked sounds and no networked phone explosions
set sv_enableNetworkedSounds false
set sv_enableNetworkedPhoneExplosions false

# State bag updates per second per player, and short spikes
set rateLimiter_stateBag_rate 75
set rateLimiter_stateBag_burst 125

If your server.cfg already turns sv_scriptHookAllowed on, remove that line. CXA overrides it while Block ScriptHookV is on, and the warning above reminds you on every start.

Recommendations

Recommended:

  • Keep the CXA defaults unless a specific script breaks.
  • Change one value at a time and test the script that had problems before changing the next one.
  • Restart the whole server after you turn an option off, so FiveM goes back to the value in server.cfg.

Avoid:

  • Allowing ScriptHookV on a public server.
  • Setting Request control filter to 0 to fix one script. Try a lower level first.
  • Setting State bag burst below State bag rate limit.

Explosion Control

  • Phone explosions are only one kind. Every other explosion type is checked by the explosion detections.
  • See Explosion Control.

Entity Control

  • The request control filter stops taking over existing entities. Entity lockdown and the entity blacklists control which entities can be created.
  • See Entity Control.

Event Guard

  • State bag limits protect state bags. Server events of your resources are rate limited by the Event Guard.
  • See Event Guard.

Modified Game Files

  • ScriptHookV loads plugins into the game; illegal RPF files change game data. CXA handles RPF files separately.
  • See Modified Game Files.

Limitations

  • These are FiveM's own settings. CXA sets them, but what each value blocks is decided by FiveM.
  • CXA cannot tell you whether FiveM accepted a value. Debug mode only shows that the value was written.
  • Turning an option off does not restore the FiveM value until the server restarts.

Common Problems

The Console Says "sv_scriptHookAllowed was on"

What you see: On every start, the console prints [CXA] sv_scriptHookAllowed was on, ScriptHookV mod menus could join. CXA turned it off, also remove it from server.cfg.

How to fix it:

  • Open server.cfg and remove the line that sets sv_scriptHookAllowed to 1 or true.
  • Restart the server. The warning no longer appears.

A Towing or Carry Script Stopped Working

What you see: Since CXA is installed, a script can no longer move vehicles or players that belong to someone else.

How to fix it:

  • Lower Request control filter by one step, save, and test the script again.
  • If it works at 0 but at no other level, keep the lowest level that works.

Sounds From One of My Scripts Are Gone

What you see: Other players no longer hear a sound that one of your scripts plays through the game.

How to fix it:

  • Turn off Disable networked sounds, save, then restart the whole server. Turning it off alone does not switch the sounds back on, because CXA does not reset the convar.

Scripts Using State Bags Lag or Lose Updates

What you see: HUD, voice or job data synced through state bags updates late, or the console shows state bag rate limit messages.

How to fix it:

  • Raise State bag rate limit and State bag burst, keeping the burst above the rate.
  • Set State bag rate limit to 0 to test with FiveM's own limits, then restart the server.

I Turned an Option Off but Nothing Changed

What you see: You switched off one of the options, but FiveM still behaves as before.

How to fix it:

  • Restart the whole server, not only the resource. CXA stops setting the convar, but the value it wrote earlier stays until the server restarts.
  • If server.cfg also sets the convar, that line applies after the restart.

I Want to Check the Current Value

What you see: You are not sure which value FiveM is using right now.

How to fix it:

  • Type the convar name alone in the server console, for example sv_filterRequestControl, to print its current value.
  • Turn on Debug mode for one start to see a Convar ... set to ... line for each value CXA wrote.

© 2026 CodeXart Studios · CXA Anticheat