Explosion Control
Cheat menus can create explosions anywhere on the map, kill players from far away or blow up the whole server at once. With OneSync, every explosion a player's game creates is sent to your server first, and CXA checks it there before the other players see it. You decide per explosion type whether CXA cancels it, logs it or punishes the player.
The Defaults Block Almost Every Type
Out of the box, every explosion type except ProgrammableAR is set to Block, so grenades, molotovs and rockets that players create are cancelled and logged. If your server uses explosive weapons, heists, ATM robberies or fireworks, review the Explosion Types table before you go live.
How It Works
Every explosion that comes from a player's game goes through these checks in this order. The first check that matches decides what happens, and the checks after it do not run.
- The player is bypassed, or a script paused
Explosionfor them: the explosion is allowed and not checked at all. - The player is being banned or kicked right now: the explosion is cancelled.
- Malformed: the explosion has no position or an impossible damage scale.
- Invisible: the explosion is marked as invisible.
- Silent: the explosion makes no sound.
- Distance: the explosion is farther away from the player than Max player distance.
- Rate limit: the player created more than Max explosions within the Window.
- Explosion type: CXA looks up the type in the types table and applies its Block, Log and Punish flags.
Types that are not in the table are allowed.
Configuration
Open Configuration → Server detections → Explosions in the panel.
| Option | Key | Default | What it does |
|---|---|---|---|
| Enabled (switch) | Enabled | true | Turns every explosion check on or off |
| Punishment (Punish types) | Punishment | ban | Punishment for types that have Punish ticked |
| Ban duration | BanDuration | 0 | Hours for that punishment, 0 = permanent |
| Screenshot | Screenshot | false | Attaches a screenshot to explosion punishments |
| Explosion types | Types | see below | Block, Log and Punish per explosion type |
| (no field in the editor) | LogChannel | Explosions | Discord channel for log results, see Log Channel and Webhook |
The special checks (invisible, silent, distance, rate limit, malformed) have their own options, explained in Special Explosion Checks.
Explosion Types
The types table lists 39 explosion types, numbered from 0 to 38. In the panel it is a table with the columns ID, Type, Block, Log and Punish. Above each column, all and none tick or untick the whole column at once.
| Flag | What it does |
|---|---|
| Block | Cancels the explosion on the server, so it is not passed on to the other players |
| Log | Writes a log entry with the detection Blacklisted explosion (Explosion) and the punishment log, and alerts staff |
| Punish | Applies Punishment (Punish types) to the player, ban by default, instead of only logging |
Punish wins over Log: a type with Punish ticked is punished even if Log is off. Block works on its own, so you can combine it freely:
| Block | Log | Punish | Result |
|---|---|---|---|
| on | on | off | Cancelled and logged. The default for most types |
| on | off | off | Cancelled without a log |
| off | on | off | Allowed, but logged. Good for watching a type before you decide |
| off | off | off | Allowed, nothing is logged |
| on | any | on | Cancelled and the player is punished |
Some rows of the default table:
| ID | Type | Block | Log | Punish |
|---|---|---|---|---|
0 | Grenade | true | true | false |
2 | StickyBomb | true | true | false |
3 | Molotov | true | true | false |
4 | Rocket | true | true | false |
5 | TankShell | true | true | true |
7 | Car | true | true | false |
9 | PetrolPump | true | true | false |
13 | DirWaterHydrant | true | false | false |
25 | ProgrammableAR | false | true | false |
35 | Firework | true | true | false |
37 | ProxMine | true | true | true |
38 | ValkyrieCannon | true | true | false |
In short: every type is blocked except 25 (ProgrammableAR), every type is logged except 13 (DirWaterHydrant), and only 5 (TankShell) and 37 (ProxMine) are punished. The full list of all 39 types is in All Settings.
In config.lua, each type is one line in Config.ServerDetections.Explosions.Types:
Types = { -- Block = cancel, Log = log only, Punish = apply Punishment
[2] = { Name = 'StickyBomb', Block = true, Log = true, Punish = false },
[5] = { Name = 'TankShell', Block = true, Log = true, Punish = true },
[35] = { Name = 'Firework', Block = false, Log = true, Punish = false }, -- example: fireworks allowed but still logged
},Special Explosion Checks
These checks run before the types table and look at how an explosion was made, not at its type. Each has its own punishment, so you can ban for invisible explosions while you only log remote ones.
| Check | Detection | Option | Key | Default |
|---|---|---|---|---|
| Malformed | Malformed explosion (ExplosionMalformed) | Block malformed explosions, Malformed explosion punishment | Malformed.Block, Malformed.Punishment | true, log |
| Invisible | Invisible explosion (ExplosionInvisible) | Block invisible explosions, Invisible punishment | Invisible.Block, Invisible.Punishment | true, ban |
| Silent | Silent explosion (ExplosionSilent) | Block silent explosions, Silent punishment | Silent.Block, Silent.Punishment | false, log |
| Distance | Remote explosion (ExplosionDistance) | Max player distance, Distance punishment | Distance.MaxDistance, Distance.Punishment | 0 (off), log |
| Rate limit | Explosion spam (ExplosionSpam) | Rate limit, Max explosions, Window, Rate limit punishment | RateLimit.Enabled, RateLimit.MaxExplosions, RateLimit.Window, RateLimit.Punishment | true, 10, 5 s, kick |
Malformed
A malformed explosion has no position (all coordinates are 0) or a damage scale above 1 or below 0. This is invalid data that normal explosions do not have, so the check cancels it by default.
Invisible
An invisible explosion damages players without any visible fire or smoke. Mod menus use them to kill players without being seen, so the default is to cancel them and ban.
Silent
A silent explosion makes no sound. The check is off by default (Block silent explosions is off). Turn it on with Silent punishment set to log first, and watch what it catches before you raise the punishment.
Distance
Max player distance is the largest distance in meters between the player and the explosion they created. 0 turns the check off, which is the default. Mod menus create explosions on players far away from the cheater. Weapons with a long range, such as rockets, also explode far from the shooter, so pick a value above the longest legal distance on your server and test it with log first.
Rate Limit
The rate limit counts the explosions one player creates within Window seconds. Every explosion above Max explosions is cancelled, and the player gets the Rate limit punishment once per window. The default allows 10 explosions in 5 seconds.
The Block Switch Turns a Check On
For Malformed, Invisible and Silent, the Block switch turns the whole check on. With Block off, CXA ignores that kind of explosion completely: it is not cancelled, not logged and not punished.
Ban durations for these checks are set in config.lua, in the same table:
Config.ServerDetections.Explosions = {
Enabled = true,
Punishment = 'ban', -- used for types with Punish = true
BanDuration = 0,
LogChannel = 'Explosions',
Screenshot = false,
Invisible = { Block = true, Punishment = 'ban', BanDuration = 0 }, -- invisible explosions (mod menus)
Silent = { Block = false, Punishment = 'log', BanDuration = 0 }, -- explosions without sound
Distance = { MaxDistance = 0.0, Punishment = 'log', BanDuration = 0 }, -- player to explosion distance, 0 = off
RateLimit = { Enabled = true, MaxExplosions = 10, Window = 5, Punishment = 'kick', BanDuration = 0 },
Malformed = { Block = true, Punishment = 'log', BanDuration = 0 }, -- no position or damage scale above 1
Types = { --[[ see Explosion Types ]] },
}Allowing Explosions From Your Scripts
Heists, ATM and bank robberies, mining jobs and firework scripts create real explosions in a player's game. With the default table, CXA cancels them. Use these steps to allow them.
Step 1 — Find the Type
Run the script once, for example blow a vault door. Open the panel's Detections tab or your Explosions Discord channel and find the Blacklisted explosion entry. The type field shows the name and ID:
[CXA] John (ID: 12) -> Blacklisted explosion [log] coords: 255.2, 225.1, 101.9, damageScale: 1.0, type: StickyBomb (2)Step 2 — Allow the Type
In Configuration → Server detections → Explosions → Explosion types, untick Block for that type. Keep Log ticked for a few days, so you still see who creates these explosions, and keep Punish unticked. Save changes.
This allows the type for every player. For types that cheaters like to use, Step 3 is the safer choice.
Step 3 — Or Pause the Check From Your Script
Keep the type blocked and let your script pause the explosion checks for the one player who is doing the heist, for a few seconds. Call it on the server, before the client part of your script creates the explosion:
-- In your heist script, on the server, right before the charge goes off
exports['cxa-anticheat']:PauseDetection(source, 'Explosion', 10) -- explosions of this player are not checked for 10 secondsWhile the pause runs, CXA does not check any explosion of that player, including invisible or remote ones, so keep the pause short. See Bypass & Pause Exports.
Step 4 — Check the Rate Limit
A firework show or a heist with several charges can create more than 10 explosions in 5 seconds. If the log shows Explosion spam for your script, raise Max explosions or let the script pause Explosion during the show.
Log Channel and Webhook
Explosion results with the punishment log go to the Explosions Discord channel. Bans, kicks and warnings from explosion checks go to the Bans, Kicks and Warns channels like every other detection.
- Set the webhook URL in the panel under Webhooks & keys → Explosions, or in
sv_config.luaasSvConfig.Webhooks.Explosions. - If the
Explosionswebhook is empty, CXA uses yourDefaultwebhook. LogChannelhas no field in the visual editor. To send explosion logs to another channel, change it inconfig.luaor paste the changed table with Import code in the panel's Code view.
Explosion logs can be frequent on a busy server. The Detection cooldown (10 seconds by default) skips repeated log results of the same player within that time, see Detections & Punishments.
Recommendations
Recommended:
- Go through the types table once and untick Block for types your server uses on purpose.
- Keep Invisible on
ban. Normal gameplay does not create invisible explosions. - Use
PauseDetection(src, 'Explosion', seconds)in heist scripts instead of allowing the type for everyone. - Set Max player distance once you know how far your legal explosions reach, then raise its punishment.
Avoid:
- Ticking Punish for common types like Grenade or Car. Cancelling them is enough, and you avoid banning honest players for a script you forgot.
- Pausing
Explosionfor long periods. The pause also skips the invisible and remote checks. - Turning off the whole Explosions switch to fix one script.
Related Features
Detections & Punishments
- Explosion checks use the same punishments, cooldowns and admin alerts as every other detection.
- See Detections & Punishments.
Blacklisted Weapons and Projectiles
WEAPON_GRENADE,WEAPON_RPG,WEAPON_GRENADELAUNCHER,WEAPON_HOMINGLAUNCHERandWEAPON_FIREWORKare in the default weapon blacklist.- Projectiles of blacklisted weapons are cancelled by the Projectiles check before they can explode.
- If your server allows these weapons, remove them from Configuration → Lists → Blacklists → Weapons as well as allowing their explosion type. See Event Guard.
Network Convars
- Disable phone explosions (
Config.Network.DisablePhoneExplosions) turns off networked phone explosions at the FiveM level. - See Network Convars.
Rule Engine
- Rules on
explosionEventcan use the fieldstype,damageScale,invisibleandaudible. - A rule can add a block or a punishment on top, but it cannot allow an explosion the types table blocks.
- See Rule Engine.
Common Problems
Grenades or Rockets Do Nothing
What you see: Players throw grenades or fire rockets, but there is no explosion for anyone else, and the logs fill with Blacklisted explosion.
How to fix it:
- This is the default: the type is blocked. Untick Block for that type (for example
0Grenade,4Rocket) in Explosion types. - Check Configuration → Lists → Blacklists → Weapons as well. Blacklisted weapons are removed and their projectiles cancelled.
My Heist Script's Explosion Is Cancelled
What you see: The vault door or ATM does not blow up, and a Blacklisted explosion log appears for the player.
How to fix it:
- Read the
typein the log and follow Allowing Explosions From Your Scripts. - If the log says Explosion spam, raise Max explosions or pause
Explosionfrom the script.
Players Are Kicked for "Explosion spam"
What you see: Players are kicked during a firefight or an event with many explosions.
How to fix it:
- Raise Max explosions or Window under Rate limit.
- Set Rate limit punishment to
logwhile you find the right value.
Explosion Logs Do Not Appear in Discord
What you see: Explosions show up in the panel, but not in your Discord channel.
How to fix it:
- Add a webhook for the
Explosionschannel in Webhooks & keys, or aDefaultwebhook. - Check that Discord webhooks is on in Configuration → Logs.
- Only
logresults go toExplosions. Bans and kicks are in theBansandKickschannels.
© 2026 CodeXart Studios · CXA Anticheat