Discord feeds

CerebRUST posts to Discord through feeds. Each one is a class of message, and each gets its own channel — so your kill feed can live in a staff channel while wipe announcements go somewhere players can see.

Set them up under Listing & Discord. Connect your Discord first, then pick a channel per feed and switch on the ones you want. Everything is off until you turn it on.

The feeds

Feed	Safe for players?	What it posts
Public events	Yes	World events (Patrol Helicopter, Cargo Ship, Bradley…) plus player join/leave.
Server lifecycle	Yes	Server online / offline / wiped announcements.
Pre-wipe announcements	Yes	Countdown hype before a scheduled wipe (10 days / 1 week / 1 day / wipe night).
Live status	Yes	One message kept up to date with players online, queue and next wipe.
Player log	No	Join/leave with a Steam profile link and a proxycheck lookup of the connecting IP.
Player reports	No	In-game F7 reports — reporter, target, type and message.
Kill feed	No	Every PvP kill — who, weapon, distance, location, sleepers. Reveals live movement.
Raid alerts	No	Raids in progress — attacker, target base and grid. Sensitive defensive info.
Team activity	No	Team created / joined / left / disbanded. Reveals group composition.
Chat mirror	No	Everything players say, plus broadcasts your staff send from the dashboard.
Sign & artwork moderation	No	Sign and artwork images with author and location.
Chat trigger alerts	No	Fires when a chat rule matches — quotes what was said.

The “safe for players” column is a judgement about what the feed reveals, not a permission setting — CerebRUST will happily post a kill feed into a public channel if you point it at one. The dashboard labels each feed the same way.

Live status

Live status is the odd one out: instead of posting a message every time something happens, it posts one message and keeps editing it, so the channel never fills up.

It carries:

Players online, and the queue if there is one
Server FPS, smoothed across the last few readings rather than the latest spike
Which day of the wipe it is, with the map size and seed
The connect address, in a code block so it is one tap to copy
The map itself — this wipe’s rendered map, as the picture on the message
A link to your public server page, which has a Connect button that launches Rust

It carries:

Players online, with the queue if there is one
Server FPS, smoothed over the last few readings rather than the instant value
Day N of the wipe, with the map size and seed
Next wipe, as a live countdown that keeps counting in your own timezone
The connect address, in a code block so it is one tap to copy
This wipe’s map, as the image
A link to your public server page — the vanity address if you have set one

It refreshes about once a minute, and only actually edits when something has changed — a quiet server produces a handful of edits an hour rather than sixty.

The FPS reading is an average of the last few samples, not a live number. CerebRUST keeps one FPS sample every five minutes, so it is a smoothed reading over roughly the last quarter of an hour — enough to tell a healthy server from a struggling one, not enough to watch a single lag spike.

If your server stops reporting, the message says so rather than leaving the last player count sitting there. A number that is quietly out of date is worse than no number, and the moment it matters most is the moment it would be wrong.

Running more than one server in one Discord

You can, and there are two sensible layouts:

A channel per server — #server-one-status, #server-two-status, and so on. Clearest if your Discord is already organised by server.
Shared channels — point both servers’ feeds at the same channel. Everything CerebRUST posts as an embed carries the server’s name in its footer, so a shared kill feed or raid feed still tells you which server each line is about.

One thing does not share well: the chat mirror posts plain lines rather than embeds, so two servers mirroring into one channel is an unreadable interleave. Give that feed a channel each.