Wipe Started
ObservedA wipe was detected from Rustexa's own observations — never from a countdown running out.
Fires only after Rustexa observes the wipe on the server itself.
Rustexa for Discord
Rustexa's bot brings the platform's canonical server, wipe and map intelligence straight into Discord — and delivers alerts the moment a wipe is observed. It reads the same data as rustexa.com, with the same distinction between what has been observed and what is merely advertised.
RRustexa/wipes
Example — wipes right now
Observed wipes and advertised schedules are shown in separate groups so a countdown is never mistaken for proof.
Rustexa · canonical wipe feed
RRustexa/map
Example — current map
Map identity is shown only when Rustexa has verified it. Unknown fields stay blank.
Rustexa · map intelligence
Commands
Nine slash commands, all free, all read-only.
/server
Full Rustexa intelligence for one server
Observed population, region, canonical wipe schedule, current map identity and network — with the evidence class shown for each value.
/server server:<name or slug>
/wipes
Wiping now, upcoming and recently observed
The same canonical wipe feed the site uses, split into observed wipes and advertised schedules.
/wipes region: type: min_players:
/map
Current map identity
Map name, type, seed and size when Rustexa has verified them. Unverified fields are left blank rather than guessed.
/map server:<name or slug>
/popular
Most populated and trending servers
Live leaderboard built from observed population, not from submitted claims.
/popular
/group
Find a Rust group recruiting
Public group profiles from Rustexa Groups, including region, playstyle and openings.
/group tag:<tag, slug or name>
/lfg
Players looking for a group
Public LFG posts with structured region and playstyle filters.
/lfg region: playstyle:
/alerts
Manage your wipe, population and schedule alerts
Private panel to link your Rustexa account, choose a destination (DM or channel) and manage every alert you subscribe to.
/alerts
/status
Rustexa data status and bot health
Live data freshness and bot connectivity, read straight from the public data layer.
/status
/rustexa
About Rustexa and every command
Quick reference for everything the bot can do inside your server.
/rustexa
Alerts
Rustexa evaluates every alert on its own infrastructure; Discord is a delivery destination, never an independent evaluator. Each alert is labelled with the kind of evidence behind it.
A wipe was detected from Rustexa's own observations — never from a countdown running out.
Fires only after Rustexa observes the wipe on the server itself.
A heads-up before an advertised wipe, with the lead time you choose. Labelled as advertised because the server may wipe early, late or not at all.
Based on the organizer's advertised or canonical schedule, not on observation.
Fires when a server crosses the player count you set — once, not every time the number wobbles across the line.
Read from observed population snapshots with hysteresis to avoid flapping.
The advertised wipe schedule for a server you track moved. Useful before a group plans a wipe day around it.
Triggered by a change in the canonical/organizer-controlled schedule.
Alerts go to your DMs or a channel you choose. Manage them with /alerts in Discord, or link your Discord account from your Rustexa account.
In Discord
Static layout examples. Real replies are filled with canonical Rustexa data at the moment you run the command.
RRustexa/server
Example — server intelligence
Rustexa · Rust server intelligence
RRustexa/popular
Example — most populated servers
A live leaderboard from observed population snapshots.
Rustexa · observed population
RRustexa/alerts
⏳ Wipe soon — example
Advertised schedule reminder with the lead time you configured.
Rustexa • Advertised schedule
Security & privacy
Rustexa asks for three permissions and one intent. That is the whole surface.
Permissions requested
Gateway intents: Guilds only. No Message Content, Presence or Server Members.
Read-only intelligence
Every command reads Rustexa's public data layer with a publishable key. The bot cannot write to your Discord server beyond posting the replies and alerts you asked for.
No message content
The bot connects with the Guilds intent only. It cannot read your messages — no Message Content intent, no message scraping, no logging of conversations.
No privileged intents
No Presence, no Server Members, no Administrator permission. It asks for View Channel, Send Messages and Embed Links, and nothing else.
No player tracking
Rustexa does not offer alerts that report where a named player is playing. There are no stalking or player-location notifications, in Discord or anywhere else.
No mass pings
Alerts post with mentions disabled. The bot never uses @everyone or @here.
You own your alerts
Linking a Discord account requires a one-time code redeemed while signed in to Rustexa. You can change destinations, pause any alert or unlink at any time.
Capabilities
Everything the bot does right now is free. Future clan tooling is being designed as new capability, not as a paywall around what already works.
Available now to every Discord server
In design — not available yet, and nothing free moves here
No billing, no subscriptions and no purchases exist yet.