Configuration overview
Where the config lives, how it is shaped, and which parts reach your server.
Read this before changing Raven settings. It covers where your config lives, the seven categories the detections are grouped into, which sections are sent to your server and which stay in the cloud.
Where the config lives
In the cloud, not in the resource folder. The package you download carries no config.json, and the self-update feed never ships one. Your config arrives in the reply to the licence check at start, again on the socket as soon as the WebSocket link comes up, and again every time you press save on the dashboard.
A save applies live, on the server and for everyone online. If the new config fails to load, the previous one is restored, so a bad save cannot leave the server unprotected. Nothing here needs a restart.
How the config is shaped
Five top-level sections, one of which holds the detections. From Raven 1.5.9.4 the detections inside Detections are grouped into seven categories, so a detection is addressed as Detections.Weapons.AntiAimbot rather than Detections.AntiAimbot.
| Section | What it holds |
|---|---|
Detections | All 74 protections, grouped into the seven categories below. |
Display | The kick and ban drop messages, the ban rejection screen, the appeal link, in-game notifications, menu alert placement, and the connection-filter rejection screen. |
ResourcesInstallation | Whether Raven manages and installs itself into your other resources, and the whitelist of resources it is kept out of. Resource 1.9.3 and newer. Older builds read AutoInstallation, with the list of resources to leave alone. |
ConnectionFilters | The on-connect pipeline: VPN, name, country and Discord filters. Needs a 1.7.3 or newer resource. |
Discord | The ban and kick webhook URLs. The cloud posts the logs, not your resource. |
The seven detection categories
| Category | Count | What it covers |
|---|---|---|
Main | 6 | Client integrity: executors, Lua menus, the NUI layer, the clipboard scanner, the screen reader and the heartbeat. |
Playerstats | 17 | What the player and their ped are doing: health and armour, movement, voice range, ped model and animations, vision modes. |
Resources | 5 | Resource tampering: starting and stopping resources, hooked natives, a tampered environment, injection into a resource. |
Entities | 24 | What gets spawned and what is done to vehicles, including the two entity flood protections and the model blacklist. |
Events | 4 | Event abuse on both sides, plus fired events and remotely played sounds. |
Weapons | 15 | Weapons and damage: aimbot, silent aim, recoil, reload and ammo, weapon spawning and blacklists, spoofed and blocked damage. |
Pyrotechnics | 3 | Explosions, particle effects and projectiles. |
What reaches your server
The resource is sent only the sections it reads, and the Discord webhook URLs are not among them. That is deliberate: those URLs are bearer tokens for your channel, and the cloud posts your ban and kick logs itself so they never have to leave it.
| Section | Sent to the resource | Note |
|---|---|---|
Detections | Yes | Applies live on save, with no restart. |
Display | Partly | The connection-filter rejection screen is served by the cloud, so it is trimmed out. |
ResourcesInstallation | Yes | All three keys, on 1.9.3 and newer. Older builds get AutoInstallation (both keys) instead. |
ConnectionFilters | Partly | Only Enable and AutoWhitelistTxAdmins. The filters themselves run in the cloud during the connection check. |
Discord | No | Dropped for 1.5.9.4 and newer, which is every current build. Older resources still posted their own webhooks and keep the section. |
GlobalBans | No | Cloud only, and not stored in the config JSON at all. |
Commands | Partly | Only AllowConsoleClear, which decides whether rac clear may be run from the server console. It is not in the shipped template, so the section exists only once you add it in the JSON editor. |
Evidence follows the same split. Screenshots and recordings are stored on the Raven CDN at ravenac.net/cdn/... and referenced by URL, so a webhook card can link to them without your server ever uploading anything to Discord. The webhook fields themselves are on Main Settings, and Discord logs covers what a card looks like.
Names that moved in 1.5.9.4
Four detections were renamed when the categories came in. The dashboard carries your Enable and Action choices across from the old name, so nothing is lost on upgrade, but ban logs written before the rename still show the old one.
| Old name | New name | Category |
|---|---|---|
ExplosionProtection | AntiExplosionAi | Pyrotechnics |
ParticleProtection | AntiParticleAi | Pyrotechnics |
AntiNuiDevTools | AntiNuiTamper | Main |
AntiOverlay | AntiExecutor | Main |
Two things called Entities
Detections.Entities is a config category, holding the detections that watch what gets spawned and what happens to vehicles. It is not the World page, which exists both on the dashboard and in the in-game admin menu and is a tool for deleting peds, vehicles and objects and messaging players. The config key keeps the name it has always had.
If your server is on an older build
Builds before 1.5.9.4 keep the flat layout, with every detection directly under Detections, and the dashboard reads both shapes. Each newer option is gated on the build that can honour it: the dashboard hides a control your resource would ignore, and trims a key it would not understand out of what it sends. The thresholds are listed on Updating Raven.