Discord integration
Channel routing
Map event families to specific channels on your Discord server.
After installing the bot, the dashboard's Discord tab gives you a routing matrix. Seven event families, one channel pick each.
| Family | What gets posted |
|---|---|
| Alerts | Smart Alarm triggers (raid alerts). |
| Events | Cargo / Heli / Chinook / Convoy / Vendor / Airdrop / Oil Rig / Deep Sea Merchant. |
| Tracking | Tracked player online/offline state changes. |
| Team chat | Mirror of in-game team chat. |
| Devices | Smart Switch / Smart Alarm state changes. |
| Players | Team login / logout. |
| Server | Server uptime / wipe time / pop changes. |
Each family has:
- A channel picker — pick from any channel the bot can see.
- An enabled switch — off = nothing routes, even if a channel is picked.
Why seven separate channels
- Some teams want raid alerts in
#raidswith @everyone, but team chat mirror in#in-game-chatwith nothing pinging. - Tracking pings go to
#intelfor the long-term enemy-watch crowd; team chat lives in#general. - Splitting them keeps each channel scannable.
Defaults
When the bot installs, it tries to auto-match channels by name:
- Channel named
rust-pulse-alerts→ Alerts. - Channel named
events→ Events. - ...
You can override any auto-match.
Per-channel rate limiting
The bot self-throttles to 5 messages per channel per 5 seconds. Bursty events (e.g. five alarms tripping at once) are collapsed into a single embed when possible. This keeps you under Discord's 50-messages-per-second guild cap with comfortable headroom.