Discord logs
The two webhooks Raven posts to, what each card carries, and why a log sometimes does not arrive.
Raven can post every ban and every kick into your own Discord channels. There are two webhooks and no others, both set in Main Settings, and both posted by the Raven cloud rather than by your FiveM resource. This page covers what each one sends, what a card contains, and what to check when nothing shows up.
The two logs
One webhook per action. A ban and a kick are separate fields, so they can point at the same channel or at two different ones.
| Log | Field in Main Settings | Posted when |
|---|---|---|
ban | Ban Webhook | A ban is filed for a player on this server, whether a detection filed it or an admin did. |
kick | Kick Webhook | A kick is filed for a player on this server, from a detection or from an admin. |
There is no screenshot webhook on a current resource. A capture is stored on the Raven CDN and its link rides inside the ban or kick card itself, so the evidence arrives with the message instead of in a separate feed.
Setting them up
Create the webhook in Discord
In the channel you want the logs in, open its integration settings and create a webhook, then copy its URL. Repeat it in a second channel if you want bans and kicks kept apart.
Open Main Settings for the server
Pick the server in the dashboard and open Main Settings. The card is called Discord Logging and sits beside Auto-Installation, which is called Resources Installation from resource 1.9.3.
Paste the URLs
Fill Ban Webhook, Kick Webhook, or both. Each field is masked like a password, with an eye button to reveal what you pasted, because a webhook URL is a secret: anyone holding it can post into that channel.
Save
Press Save Changes. Anything that is not an https discord.com or discordapp.com webhook path raises an error as you type, and a save still carrying one is refused rather than stored. Leaving a field empty turns that log off.
What a card contains
Both logs use one layout. The title is Player Banned or Player Kicked, with (Manual) appended when a person filed it rather than a detection.
| Row | What it holds |
|---|---|
| Player | The name the resource reported, or Unknown. |
| By | Who filed it: the server console, an in-game admin, a dashboard operator, or a resource. Absent on a detection, which has no actor. |
| Reason | The ban or kick reason, or "No reason provided." |
| Screenshot / Record | A download link to the capture. A capture that came back empty says so in words instead of linking a black image. |
| Steam | The hex id, linked to the Steam profile. |
| IP Address | Hidden behind a spoiler, linked to a lookup. |
| Discord | A mention of the linked account. |
| Live, Xbox, License | The raw identifiers, prefix included. |
| Ban Id / Kick Id | The id of the row, present on whichever of the two applies. |
| Additional Info | One key per line, exactly as the dashboard shows it: the detection context, or for a kick or ban a person filed, who issued it and from where. |
What ends up in Additional Info, and how to turn it into a config change, is covered on Reading a detection.
When a log does not arrive
Delivery is best effort and never blocks the ban itself, so a missing card is always a configuration problem rather than a missed action. The action is still on your Bans List or in the activity log either way.
- Nothing at all for one action type. That field is empty. A blank webhook is a silent no-op by design, so check the other field is not the only one filled in.
- Nothing after the channel or webhook was changed. A deleted webhook answers with a not-found and Raven stops rather than retrying, on the assumption that a removed webhook was removed on purpose. Create a new one and re-paste it.
- The card looks like the older embed. Some guilds refuse the newer card layout. Raven detects the refusal once and falls back to the embed for the rest of that process, so the log keeps arriving in the shape it always had.
- A recording arrives as a link rather than a player. The card layout cannot carry an uploaded file, so a clip is a Download link and the card shows the Raven banner. Screenshots are CDN images and still render inline.
Servers below resource 1.5.9.4
An older resource posts its own Discord logs from its own config rather than having the cloud do it, and the dashboard shows it a different card for that reason: a Discord Integration card with three plain fields, Kick Webhook, Ban Webhook and Screenshot Webhook. The screenshot field only exists on that path. Updating the resource moves logging to the cloud, which is what lets the capture link ride inside the ban and kick cards.