Your first hour of tuning
The settings to change before you open the server, in the order that stops the most false bans.
Last updated
Raven works out of the box, but the defaults cannot know which resources on your server legitimately spawn props, what voice ranges your voice script uses, or that your custom weapons are yours. Those are the gaps that produce the first wave of appeals, and all of them are fixable in about an hour before anyone connects.
What needs a decision before you open
Plenty of detections ship enabled on ban with an empty whitelist, but four of them turn on a list the shipped defaults could not have filled in for you: your spawning resources, your word list, your voice ranges and your addon weapon names. Those are the four to deal with. Everything else can wait until the logs tell you it needs attention.
| Detection | Ships as | What it needs from you |
|---|---|---|
EntitiesSpamProtection | on, ban | Your spawning resources in its whitelist. It ships with an empty whitelist and bans on the first rule that trips. |
ClipboardScanner | on, ban | A pruned word list, or the action dropped to kick. Short generic words on the shipped list also match ordinary text. |
AntiVoiceSpoofing | on, ban | Every proximity value above 50 that your voice script sets. Only 80 and 250 are permitted out of the box. |
AntiSpawnWeapons | on, ban | Your addon weapon names, so Raven recognises them as real weapons instead of unknown hashes. |
The four changes
Whitelist your spawning resources
Do this one first. Entities Spam Protection counts the entities each player creates and bans when a rule trips, and the rule that catches legitimate scripts is the plain count per type.
| Entity type | Entities | Within |
|---|---|---|
Objects | 25 | 10 seconds |
Vehicles | 20 | 10 seconds |
Peds | 15 | 10 seconds |
An inventory script dropping a large stash on the floor, a garage pulling several vehicles out at once, or a prop-placement tool laying out an event can all cross those lines in normal use.
Add your own resources to the whitelist. The name is matched against the resource that created the entity, so enter the resource name as it appears in your server, such as ox_inventory or your garage script.
Detections.Entities.EntitiesSpamProtection.WhitelistResourcesDo the same for Detections.Entities.EntitiesSpawnProtection.WhitelistResources if you turn that detection on later. Whitelisting the resource is always better than raising a threshold: the threshold applies to everybody, the whitelist applies to the one script you trust.
Settle the clipboard scanner
Clipboard Scanner catches pasted text that matches its word list. Some of the shipped entries are ordinary English fragments, so ordinary text can match them.
| Shipped entry | Ordinary text that matches it |
|---|---|
print | sprint, footprint, printer, blueprint |
script | description, subscription, scripted, and any Discord blurb containing the word script |
_g | any identifier carrying it, such as my_group or veh_garage |
Pick one of these before you open:
- Remove the short generic entries from
Detections.Main.ClipboardScanner.Wordsand keep the FiveM specific ones liketriggerserverevent,networkrequestcontrolofentityandloadresourcefile, which no player types by accident. - Or set
Detections.Main.ClipboardScanner.Actiontokickand read the logs for a week before putting it back toban.
The pasted text is usually attached to the log entry, so the first few hits tell you straight away whether the match was a cheat or a word.
Whitelist your voice ranges
Anti Voice Spoofing catches a voice range set above the ceiling and not in the permitted list, and bans for it. The permitted list is an exact number match, not a range: if your voice script sets a shout tier to 120, every player who shouts is banned, because 120 is neither 80 nor 250.
| Field | Ships as | Meaning |
|---|---|---|
Maximum | 50 | Anything at or below this is never questioned. |
Whitelist | 80, 250 | Exact values permitted above the ceiling. Add every proximity above 50 your voice script sets. |
Open your voice resource, read the proximity values it sets, and add every one of them that is above 50. If it only uses the stock ranges, the shipped values are already correct and there is nothing to do.
Detections.Playerstats.AntiVoiceSpoofing.WhitelistRegister your addon weapons
If your server has addon weapons, Raven needs to be told they exist. There are two lists and they do opposite things, so read this before typing.
| List | What it does | Accepts |
|---|---|---|
AddonWeapons | Enrols | Weapon names only. A numeric hash pasted here is silently ignored, so the weapon stays unknown and the bans continue. |
WhitelistWeapons | Exempts | A weapon name or a numeric hash. This is the list that stops the detection firing. |
Putting a weapon in AddonWeapons expecting it to be permitted is the wrong way round and causes the bans you were trying to prevent. Both lists live under Detections.Weapons.AntiSpawnWeapons.
Expect Anti Godmode in your damage logs
Anti Godmode catches players who cannot take damage. It can show up in your injury system, damage webhook, armour tracking and death cam, so expect to see it there.
If it is noisy in a hospital, a spawn area or a safe zone, whitelist that zone.
Detections.Playerstats.AntiGodmode.WhitelistZonesAnti Godmode is also one of the three detections that ships on kick rather than ban. Leave it there until you have watched it for a while. The other two are listed on What Raven ships with.
The three decisions you can defer
Twelve detections ship switched off, and nothing turns them on for you. Most are off because they only apply to some servers, but three need a decision. The full list of twelve is on What Raven ships with.
Entities Spawn Protection
Off by default. Where Entities Spam Protection counts how many things a player creates, this one judges the individual spawn rather than the rate, across pickups, peds, vehicles and objects, with all four types enabled the moment you switch it on. If you enable it, whitelist your spawning resources first, exactly as in the first change above. Whitelisting the resource or the model is always better than switching off a whole entity type. There is a page of its own for it: Entities Spawn Protection.
Anti Speed Hack
Off by default. Its thresholds are not configurable. The only settings are the three type switches and a zone whitelist.
| Type | What it catches |
|---|---|
Normal | Moving too fast on foot. |
Water | Swimming too fast. |
Climb | Climbing too fast. |
A sprint or parkour script can trip the Normal check, and you cannot raise the bar. If you run one, enable Water first, watch Normal in the logs on kick, and only then trust it.
Anti Screen OCR
Off, and that is the right setting for almost every server. It catches cheat menus shown on the player's screen, matched against a word list. Your own job UI, your vehicle names and your chat put text on screen too, so a loose word list can match them.
If you are hunting one specific menu, set the word list to that menu's full option labels, at least three of them, set the action to kick, and review the evidence for a week first. Every hit is saved as a screenshot with the matched words boxed in red, so you can check it before you trust it.
The order to do it in
Whitelist your spawning resources
Inventory, garages, prop tools and anything else that creates entities, into Entities Spam Protection.
Settle the clipboard scanner
Prune the word list or drop it to kick. It ships on ban.
Add your voice ranges
Every proximity value your voice script sets above 50.
Register addon weapons
Names, not hashes, and know which of the two lists you mean.
Open the server and watch
Leave everything else alone for a week. Read the Activity log daily and fix what fires rather than what you think might.
Then escalate
Move anything you moved to kick back to ban once it has been quiet, and turn on the deferred detections one at a time.
Once bans start arriving, Reading a detection turns a log entry into the config change that stops it, and Review a false ban covers the appeal side.