Entity Control
Entities are everything that exists in the game world: vehicles, peds (characters) and objects (props). Cheaters spawn tanks and cargo planes, fill the map with hundreds of props or build cages around other players. With OneSync, every networked entity a player's game wants to create is announced to your server first, and CXA checks it there before anyone else sees it.
Your Scripts Spawn Entities Too
The default blacklists contain models that some servers use on purpose, for example ATM and gas pump props (prop_atm_01, prop_gas_pump_1a) and the train (freight). If your scripts spawn any listed model, remove it from the list before you raise a punishment, or those scripts stop working.
How It Works
- When a player's game creates a networked entity (one that other players can see), the server receives it before it exists for anyone else.
- The player whose game creates the entity is its owner. CXA punishes the owner, never the players around it.
- CXA knows whether a script created the entity or the game created it by itself as traffic or ambient population. Several checks only punish script spawns, so normal traffic never gets a player in trouble.
- Entities of bypassed players are not checked.
- Entities that exist only on one player's screen (non-networked props) never reach the server, so server checks do not see them.
Entity Blacklist
The entity blacklist cancels every networked vehicle, ped or object whose model is on one of your lists. A cancelled entity is never created for anyone. It costs a single table lookup per entity.
Open Configuration → Server detections → Entity blacklist.
| Option | Key | Default | What it does |
|---|---|---|---|
| Enabled (switch) | Config.ServerDetections.EntityBlacklist.Enabled | true | Turns the blacklist on or off |
| Punish only script spawns | PunishOnlyScriptSpawned | true | Traffic and ambient spawns of a listed model are cancelled but never punished |
| Vehicles: enabled | Vehicles.Enabled | true | Checks vehicles against the vehicle list |
| Vehicles: punishment | Vehicles.Punishment | log | Punishment for a blacklisted vehicle spawn |
| Peds: enabled | Peds.Enabled | true | Checks peds against the ped list |
| Peds: punishment | Peds.Punishment | log | Punishment for a blacklisted ped spawn |
| Objects: enabled | Objects.Enabled | true | Checks objects against the object list |
| Objects: punishment | Objects.Punishment | log | Punishment for a blacklisted object spawn |
| (no field in the editor) | LogChannel | Entities | Discord channel for log results |
The detections are logged as Blacklisted vehicle spawn (BlacklistedVehicle), Blacklisted ped spawn (BlacklistedPed) and Blacklisted object spawn (BlacklistedObject). Player characters are never matched, even if their model is on the ped list. BanDuration and Screenshot for each kind can be set in config.lua:
Config.ServerDetections.EntityBlacklist = {
Enabled = true,
PunishOnlyScriptSpawned = true, -- ambient/traffic spawns are blocked but never punished
LogChannel = 'Entities',
Vehicles = { Enabled = true, Punishment = 'log', BanDuration = 0, Screenshot = false },
Peds = { Enabled = true, Punishment = 'log', BanDuration = 0, Screenshot = false },
Objects = { Enabled = true, Punishment = 'log', BanDuration = 0, Screenshot = false },
}The Lists
The models live in three lists under Configuration → Lists → Blacklists. Write each model with its spawn name, for example rhino.
| List | Key | Default entries | Examples |
|---|---|---|---|
| Vehicles | Config.BlacklistedVehicles | 8 | cargoplane, rhino, buzzard, avenger, luxor, blimp2, freight, jugular |
| Peds | Config.BlacklistedPeds | 21 | s_m_y_swat_01, a_c_chimp, a_c_killerwhale, u_m_y_zombie_01 |
| Objects | Config.BlacklistedObjects | 159 | Gas pumps, ATMs, stunt ramps, downtown building models such as dt1_05_build1_damage, prop_ld_toilet_01 |
The panel accepts up to 1000 vehicles, 1000 peds and 3000 objects.
Never Blacklist the Player Models
Do not add mp_m_freemode_01 or mp_f_freemode_01 to the ped list. They are the default player models. With Blacklisted player model on, every player who uses them would be flagged.
Client Checks That Use the Same Lists
Two client detections read the same lists and cover what the server blacklist cannot see. Both are off by default and use log.
| Detection | Key | What it catches |
|---|---|---|
| Blacklisted vehicle use | BlacklistedVehicleUse | A player sits in a vehicle from the vehicle list. With Delete vehicle on, the vehicle is deleted when the player is the driver |
| Blacklisted player model | BlacklistedPlayerModel | A player uses a model from the ped list as their own character |
You find them under Configuration → Client detections.
Entity Spam
Entity spam counts the entities each player creates and stops a player who suddenly creates far too many, which is how mod menus lag or crash a server.
Open Configuration → Server detections → Entity spam.
| Option | Key | Default | What it does |
|---|---|---|---|
| Punishment | Punishment | log | What happens to the spammer |
| Window | Window | 5 s | Length of the counting window |
| Max entities | MaxEntities | 160 | Entities one player may create per Window |
| Count only script spawns | CountOnlyScriptSpawned | true | Ignores traffic and ambient population |
| Block excess | BlockExcess | true | Cancels every entity above the limit |
| Cleanup on detection | CleanupOnDetection | false | Deletes every entity the spammer created when the detection fires. Marked [PERF]: it loops over every server entity once |
The player gets the punishment once per window, logged as Entity spam (EntitySpam) in the Entities channel.
Entity Lockdown
Entity lockdown is a protection built into FiveM's OneSync. Instead of checking entities one by one, it stops players' games from creating entities at all, so only your server can spawn them.
It works per routing bucket. A routing bucket is a separate copy of the game world on the same server: players in different buckets cannot see each other or each other's entities. Everyone starts in bucket 0, and scripts move players to other buckets for things like apartments, character creation or private instances.
Open Configuration → System → Entity lockdown.
| Option | Key | Default | What it does |
|---|---|---|---|
| Enabled (switch) | Config.EntityLockdown.Enabled | false | Applies the mode when the anticheat starts |
| Mode | Mode | relaxed | How strict the lockdown is, see below |
| Routing buckets | Buckets | { 0 } | The buckets the mode applies to |
| Mode | Panel label | What players' games may still create |
|---|---|---|
relaxed | Relaxed | Entities the game creates by itself, such as traffic and pedestrians. Entities created by client scripts are blocked |
strict | Strict | Nothing. Every entity must be created by the server |
inactive | Inactive | Everything, FiveM's normal behavior |
What Breaks With Lockdown
In relaxed mode, every script that spawns networked vehicles, peds or objects from the client side stops working, for example garages, job vehicles or furniture scripts written that way. They must spawn those entities on the server instead, for example with CreateVehicleServerSetter. In strict mode, traffic and pedestrians that players' games would create also stop appearing. Test on a copy of your server first.
CXA sets the mode once, when it starts. Turning the switch off later does not undo a mode that was already set. To undo it, choose Inactive and save, or restart the whole server.
Other Entity Checks
These server detections look at entities in other ways. All of them are under Configuration → Server detections.
| Detection | Key | Default | What it does |
|---|---|---|---|
| Objects attached to players | AttachedObjects | kick | Finds objects and vehicles that another player attached to someone, used for cages and trolling |
| Invisible entities | InvisibleEntity | log | Flags entities that are still invisible a moment after they spawn |
| Malformed entities | MalformedEntity | log | Cancels entities created with invalid data (no model) |
| Particle spam | ParticleSpam | kick | More than 30 particle effects from one player in 5 seconds |
| Fire spam | FireSpam | kick | More than 20 fires from one player in 5 seconds |
Objects Attached to Players
Every Scan interval (5000 ms), CXA looks at every networked object and vehicle. If one is attached to a player but controlled by a different player's game, CXA deletes it (Delete the object, on by default) and punishes the player whose game controls it. The check is marked [PERF] because it scans every networked object and vehicle each interval; keep the interval at 5000 ms or higher on big servers. If one of your scripts attaches props or vehicles to another player from the attaching player's game, test it with log first.
Invisible Entities
Mod menus can spawn props and vehicles that nobody can see. CXA waits Check delay (1500 ms) after an entity spawns and flags it if it is still invisible. Some scripts spawn hidden props on purpose, so the default is log with Delete the entity off. Add those models to Ignored models.
Malformed Entities
An entity without a valid model cannot come from normal gameplay. CXA always cancels it and applies the punishment.
Particle and Fire Spam
Both checks count networked particle effects (ptFxEvent) or fires (fireEvent) per player. With Block on (the default), every effect or fire above the limit is cancelled, and the player gets the punishment once per window.
| Option | Particle spam key | Fire spam key | Defaults |
|---|---|---|---|
| Window | ParticleSpam.Window | FireSpam.Window | 5 s for both |
| Max particles / Max fires | ParticleSpam.MaxParticles | FireSpam.MaxFires | 30 / 20 |
| Block | ParticleSpam.Block | FireSpam.Block | true for both |
Vehicle Protection
A few more checks protect vehicles and the players inside them:
| Check | Where it runs | Default | What it stops |
|---|---|---|---|
Clear ped tasks (ClearPedTasks) | Server | kick | Kicking other players out of their vehicles or freezing them |
Vehicle ram (AntiRam) | Client finds it, server confirms | off, log | Driverless vehicles flying at players. The vehicle is deleted and its creator punished |
Vehicle carry / throw (VehicleCarry) | Client | ban | A vehicle attached to the player, used by menus that lift and throw cars |
Request control filter (Config.Network.FilterRequestControl) | FiveM | 2 | Players taking control of other players' entities, such as hijacking a vehicle. See Network Convars |
Recommendations
Recommended:
- Remove every model your scripts spawn from the lists before you go live, especially ATMs, gas pumps and job vehicles.
- Keep Punish only script spawns on. Traffic can contain listed models, and players cannot control traffic.
- Start Entity spam and Invisible entities on
log, then raise them once you know your scripts stay below the limits. - Use entity lockdown only when all your scripts spawn entities on the server.
Avoid:
- Adding the freemode player models to the ped list.
- Turning on Cleanup on detection on a high-population server without testing it.
- Switching entity lockdown to strict on a live server without testing it first.
Related Features
Detections & Punishments
- Entity checks use the same punishments, cooldowns and admin alerts as every other detection.
- See Detections & Punishments.
Rule Engine
- Rules on
entityCreatingcan use the fieldsmodel,type(1 ped, 2 vehicle, 3 object) andscript. - Use them for conditions the lists cannot express, for example blocking a model only when a script spawned it.
- See Rule Engine.
Network Convars
- Request control filter stops players from taking over entities that belong to others.
- See Network Convars.
Event Guard
- Sound abuse and the other game event checks are explained there.
- See Event Guard.
Common Problems
Vehicles From My Garage or Job Disappear
What you see: A vehicle spawns for a moment or not at all, and the log shows Blacklisted vehicle spawn.
How to fix it:
- Remove the model from Configuration → Lists → Blacklists → Vehicles.
- If entity lockdown is on, the script spawns the vehicle on the client. Move the spawn to the server or set Mode to Inactive.
Props From My Script Are Not Created
What you see: A housing, robbery or job script cannot place its props.
How to fix it:
- Check the log for Blacklisted object spawn and remove the model from the object list. ATMs and gas pumps are on it by default.
- If the log shows Entity spam, the script creates many props at once. Raise Max entities.
- If Invisible entities has Delete the entity on and the script spawns hidden props, add the model to Ignored models.
Traffic and Pedestrians Are Gone
What you see: The streets are empty after you turned on entity lockdown.
How to fix it:
- Strict mode blocks every entity players' games create, including traffic. Use Relaxed, or Inactive if your scripts need client spawns.
- If you turned the switch off and nothing changed, choose Inactive and save, or restart the server. A mode that was set once stays until it is changed.
Players Are Kicked for "Attached objects to a player"
What you see: Players are kicked with Attached objects to a player while using a script.
How to fix it:
- Use the
modelandvictimdetails in the log to find the script that attaches a prop or vehicle to another player. - Set Objects attached to players to
logwhile you test, or turn it off if your scripts attach entities to other players on purpose.
© 2026 CodeXart Studios · CXA Anticheat