Your first hour of tuning

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.

1. Tell Raven which of your resources are allowed to spawn things

This is the single most valuable change on the page. Entities Spam Protection ships on, set to ban, with an empty whitelist, and its object rule fires at 25 objects in 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 that line in normal use.

Add your own resources to the whitelist. The list is matched against the resource that actually created the entity, so the name to enter is the resource name as it appears in your server, such as ox_inventory or your garage script.

Detections.Entities.EntitiesSpamProtection.WhitelistResources

Do 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.

2. Decide what to do about the clipboard scanner

Clipboard Scanner ships on and set to ban. It watches text pasted into Raven's own interface and bans on the first match against its word list, with no second chance. The match is a plain substring test, not a whole word, and the shipped list includes short generic entries.

Pick one of these before you open:

• Remove the short generic entries from Detections.Main.ClipboardScanner.Words and keep the FiveM specific ones like triggerserverevent, networkrequestcontrolofentity and loadresourcefile, which no player types by accident.
• Or set Detections.Main.ClipboardScanner.Action to kick and read the logs for a week before putting it back to ban.

3. Whitelist your voice ranges

Anti Voice Spoofing ships on and set to ban, with a ceiling of 50 and exactly two permitted values above it, 80 and 250. 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 not 80 and is not 250.

Open your voice resource, read the proximity values it actually sets, and add every one of them that is above 50.

Detections.Playerstats.AntiVoiceSpoofing.Whitelist

If your voice script uses only the stock ranges, the shipped values are already correct and there is nothing to do.

4. Register your custom 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 carefully before typing:

• AddonWeapons enrols a weapon in Anti Spawn Weapons checking. Put your custom weapons here so Raven recognises them as real weapons rather than unknown hashes. Entries must be the weapon name; a numeric hash pasted here is silently ignored.
• WhitelistWeapons exempts a weapon. This is the list that stops a detection firing. It accepts a name or a hash.

Putting a weapon in AddonWeapons expecting it to be permitted is the wrong way round and causes the bans you were trying to prevent.

5. Expect Anti Godmode in your damage logs

Anti Godmode does not watch for damage, it tests for it. About every 45 seconds it fires a single point of damage at the player with a pistol, checks whether their health or armour moved, and immediately restores whatever it took. Pain audio and blood are suppressed, so the player sees nothing.

Your injury system, damage webhook, armour tracking and death cam do see it, as a self-inflicted one damage pistol hit per player every 45 seconds. If that is noisy for you, the probe is skipped entirely inside a whitelisted zone, which makes it the right tool for a hospital, a spawn area or a safe zone.

Detections.Playerstats.AntiGodmode.WhitelistZones

Anti 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.

6. Consider turning two things on

Thirteen detections ship off. Most are off because they only apply to some servers, but two are worth a deliberate decision on day one.

Entities Spawn Protection

Off by default, and it is the detection the rest of the docs point at as the fix for a spawn flood. If you turn it on, whitelist your spawning resources first, exactly as in step one. Whitelisting the resource or the model is always better than switching off a whole entity type.

Anti Speed Hack

Off by default and one of the most requested checks. The on foot threshold sits close to what modified sprint scripts and parkour resources produce, so if you run either of those, enable the water check first and watch the on foot one before trusting it.

7. Leave the screen reader off

Anti Screen OCR ships off, and that is the right setting for almost every server. It reads the text drawn on the player's screen every few seconds and bans on the first match against a list of 117 words, with no second chance. That list contains ordinary English: trigger, execute, destroy, invisible, spectate, explosion. Your own job UI, your vehicle names and your chat will all put those words on screen.

If you are hunting one specific menu, cut the word list down to that menu's brand names only, set the action to kick, and review the evidence screenshots for a week first. Every hit is saved with the matched words boxed in red, so you can check it before you trust it.

The order to do it in