Rustexa for Discord

Run your wipe day from Discord

Server, wipe, population and map intelligence. A private search for the next wipe worth playing. Alerts on the servers you follow. And full clan operations — participation, ready checks, tasks, assignments and a live wipe room — all reading and writing the same canonical Rustexa data as the website.

Add Rustexa to Discord Read the FAQ

No message content access
No presence or voice tracking
No Administrator permission

RRustexa/operationboard

Example — live wipe room

Layout example. The real dashboard is filled from your clan's canonical operation.

Going: participation counts
Ready: ready-check counts
Tasks: done / total
Role gaps: coverage, e.g. Pilot 0 / 1

Rustexa · Clan Operations

GoingReadyTasksRefresh

RRustexaAlert

Wipe started — example

Alert layout example. Wipe started only ever fires from an observed wipe.

Players: observed at wipe
Map: verified when known
Observed: relative timestamp

Rustexa • Observed wipe

Open serverManage alerts

Command directory

Every command the bot registers — 19 in total

Each entry lists its exact options, who can run it, whether the reply is private, and the buttons it opens.

/server
Full Rustexa intelligence for one server
Public
Observed population, region, wipe timing with its evidence label, current map identity and network. Values Rustexa cannot verify are shown as unknown rather than guessed.
/server server:<name or slug>
FAQ
/wipe
Last and next wipe for one server, with evidence
Public
Wipe intelligence for a single server: the most recent observed wipe and the next known wipe, each carrying its evidence label. No wipe time is ever invented.
/wipe server:<name or slug>
FAQ
/wipes
Wipes happening now, upcoming and recently observed
Public
The canonical wipe feed, grouped so an advertised countdown is never mistaken for an observed wipe.
/wipes [region] [type] [min_players]
FAQ
/findwipe
Find a server to play, by wipe timing
Public
An interactive private search across the canonical wipe feed. Refine timing, region, type and population from buttons in the reply, and page through the results.
/findwipe [when] [region] [type] [min_players]
Private replyFAQ
/population
Current population and recent trend
Public
Observed population snapshots and the recent trend for one server. Rustexa reports what it observed; it does not estimate or predict population.
/population server:<name or slug>
FAQ
/map
Current map identity
Public
Map name, type, seed and size when Rustexa has verified them. Unverified fields are left blank rather than guessed, and no map imagery is rendered.
/map server:<name or slug>
/popular
Most populated and trending servers
Public
The same live ranking the Rustexa homepage uses, built from observed population.
/popular
/tracked
Your tracked servers, with population and wipe timing
Linked account
A private view of the servers you follow on Rustexa, with live population and wipe timing, plus controls to untrack. Tracking lives on your Rustexa account — Discord is a view and a remote.
/tracked
Private replyFAQ
/alerts
Manage where your Rustexa alerts are delivered
Linked account
A private panel to link your Discord account to Rustexa, pick a destination (direct message or a channel) and manage each alert you subscribe to.
/alerts
Private replyFAQ
/operation
Your clan's current or next operation
Clan member
A private panel showing the operation, participation, the ready check, tasks, assignments and role coverage — and your own Going / Maybe / Not going and Ready / Not ready response.
/operation [clan]
Private replyFAQ
/operationboard
Pin a live operation dashboard in this channel
Clan leadership
Creates one persistent dashboard for an operation in the current channel. It requires the canonical Rustexa clan permission to manage operations; Discord roles, server ownership and Administrator grant nothing. Asking twice returns the existing dashboard instead of posting another one.
/operationboard operation:<operation>
Private replyFAQ
/group
Find a Rust group recruiting
Public
Public group profiles from Rustexa Groups, or the directory when no tag is given.
/group [tag]
/lfg
Players looking for a group
Public
Public LFG posts with structured region and playstyle filters.
/lfg [region] [playstyle]
/farm
Farm cost for a loadout of explosives
Public
The raw materials behind a loadout of rockets, C4, explosive ammo and satchels, worked out by the same Farm Calculator engine the website uses.
/farm [rockets] [c4] [explosive_ammo] [satchels]
FAQ
/raid
Explosives and sulfur needed to break a wall or door
Public
Cost to break one raid target, using the website's own Raid Calculator. The optimisation used is always stated, and unsupported targets are never invented.
/raid target:<wall or door> [amount] [method]
FAQ
/smelt
Smelting time and output for an amount of ore
Public
Time, output and slot plan for a furnace run. Fuel needed and charcoal returned are deliberately absent: Rustexa has no verified numbers for them and will not guess.
/smelt ore:<what you are smelting> amount:<how much> [device] [slots]
FAQ
/recycle
What an item gives back, and which recycler is best
Public
Recycler output for any recyclable item across all four recyclers, with guaranteed returns kept separate from chance returns. An average is never shown as guaranteed.
/recycle item:<what you are recycling> [amount] [recycler]
FAQ
/status
Rustexa data status and bot health
Public
Live data freshness and bot connectivity, read straight from the public data layer.
/status
/rustexa
About Rustexa and the available commands
Public
A quick reference for what the bot can do inside your server.
/rustexa

Buttons & menus

Actions are not commands

These appear inside replies and dashboards. They are listed separately so nobody goes looking for a slash command that does not exist.

Wipe discovery

Refine timing / region / typePublic
Narrows a /findwipe search in place
Next / previous pagePublic
Pages through wipe results
Track serverLinked account
Adds the server to your Rustexa tracked list

Participation

Going / Maybe / Not goingClan member
Your own participation response only
Ready / Not readyClan member
Your own answer to an open ready check

Operation management

Open / close ready checkClan leadership
One open ready check per operation
Mark task done / reopenClan member
Requires the canonical task permission
Create / remove assignmentClan leadership
Requires the canonical readiness permission
Refresh dashboardClan member
Redraws the live wipe room from canonical state

Emergency

Defense / Urgent operation / Clan emergencyClan leadership
Manual, confirmed, leadership-only

Clan operations

Discord is a client, not a second clan system

Every action you take in Discord reads and writes the same canonical operation the website shows. There is no separate Discord-only state to reconcile.

Operation

A planned clan event, usually a wipe day, with a lifecycle, optional canonical wipe link, participation, tasks and assignments.

More in the FAQ

Participation

Going, Maybe, Not going — or No response. Silence is never converted into a decision.

More in the FAQ

Ready check

A short window opened right before an operation asking who is ready now. One open at a time.

More in the FAQ

Going is not Ready

Going is an intention given in advance. Ready is a separate answer to a live ready check.

More in the FAQ

Tasks

Required or optional units of work, filterable by Open, Mine, Required and All, markable done from Discord with permission.

More in the FAQ

Assignments

A named member given responsibility. Leadership creates them and the assignee is notified.

More in the FAQ

Role coverage

Whether the gameplay roles the operation wants are present, e.g. Pilot 0 / 1. Coverage is not the same as an assignment.

More in the FAQ

Permissions are Rustexa's

Leadership actions check your clan role on Rustexa. Discord Administrator grants nothing.

More in the FAQ

Live wipe room

One pinned dashboard, one source of truth

Leadership pins /operationboard in a channel. It redraws whenever the operation changes, so the clan reads one picture instead of a scroll of messages.

Shows the operation, server, start, lifecycle state, participation counts, ready-check counts, role gaps and task progress.
One dashboard per operation and channel — running the command again returns the existing one.
Updates automatically when the operation changes, with a manual refresh button as well.
Personal actions answer you privately; only aggregate counts appear on the shared board.
Requires the Rustexa clan permission to manage operations, and cannot be created in a DM.

RRustexa/operationboard

Example — pinned operation dashboard

Layout example only. Real values come from your clan's canonical operation.

Operation: name and state
Server: canonical server
Start: confirmed or planned, labelled
Going: participation counts
Ready: ready-check counts
Tasks: done / total

Rustexa · updates when the operation changes

GoingMaybeNot goingReadyTasksRefresh

Notifications

Rustexa decides, Discord delivers

Rustexa evaluates every notification on its own infrastructure and labels the evidence behind it. Discord is a delivery destination, never an independent evaluator.

Wipe Started

Observed

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.

Wipe Soon

Advertised

A heads-up before an advertised wipe, with the lead time you choose. The server may still wipe early, late or not at all.

Based on the advertised or canonical schedule, not on observation.

Schedule Changed

Advertised

The advertised wipe schedule for a server you track moved.

Triggered by a change in the canonical schedule.

Population Threshold

Observed

Fires when a server crosses the player count you set — once, not on every wobble.

Read from observed population snapshots, with hysteresis so it does not flap.

Operation Assignment

Canonical

You were given an assignment on a clan operation.

Raised by the operation itself when an assignment is created for you.

Ready Check Opened

Canonical

Your clan opened a ready check and is waiting on answers.

Raised when leadership opens a ready check on an operation.

Emergency Clan Alert

Manual

Leadership raised a Defense, Urgent operation or Clan emergency alert.

Human-triggered by authorized clan leadership. Never automatic.

Choose a direct message or a channel with /alerts, or manage families, channels and quiet hours in your notification settings. Quiet hours hold external delivery; the notification still lands in your Rustexa inbox.

Emergency alerts

Manual, leadership-only, always human

Rustexa does not claim automatic raid detection. An emergency alert is raised deliberately by authorized clan leadership, requires confirmation, and is rate limited.

Defense

Get people back to base now

Urgent operation

Something needs the team immediately

Clan emergency

Anything else the clan must know now

Alerts reach the clan's current members through each member's own notification preferences, with an optional short reason. Mentions stay disabled — no @everyone, no @here.

Wipe honesty

What a wipe time actually means

Rustexa uses one vocabulary everywhere — website, alerts and Discord — so an advertised countdown is never mistaken for an observed wipe.

Confirmed server wipe

An exact time supported by qualifying canonical evidence. Only this label gets an exact countdown.

Clan planned time

A time your clan chose for planning. It is your plan, not the server's published time.

Time not published

The date is known but no trustworthy exact time exists. Rustexa shows the date and stops there.

No anchor set

No supported time anchor is available at all, so nothing is shown as a time.

An advertised hour without a trustworthy timezone stays a date, not a time. Rustexa does not pick an hour on the organizer's behalf. How wipe evidence works

In Discord

What it looks like in your server

Static layout examples. Real replies are filled with canonical Rustexa data at the moment you run the command.

RRustexa/server

Example — server intelligence

Players: observed population
Region: canonical region
Network: classified network
Next wipe: labelled by evidence
Current map: verified identity
Last seen: observation freshness

Rustexa · Rust server intelligence

Open on RustexaTrack server

RRustexa/findwipe

Example — find a wipe to play

A private, refinable search across the canonical wipe feed.

Result 1: server · timing · players
Result 2: server · timing · players
Result 3: server · timing · players

Rustexa · canonical wipe feed

TimingRegionTypeNext pageTrack

RRustexa/operation

Example — your next operation

Private panel. Your response is yours; only counts are shared.

Start: confirmed or planned, labelled
Participation: going / maybe / not going
Ready check: open or closed
Tasks: open / done

Rustexa · Clan Operations

GoingMaybeNot goingTasksAssignments

Getting started

From nothing to a live wipe room

Public lookups work immediately. Tracking and clan operations need a linked account.

01
Create or sign into Rustexa
Your account holds tracking, alerts and clan membership.
Open
02
Link Discord
Run /alerts in Discord for a one-time code, then redeem it while signed in to Rustexa.
03
Add the Rustexa bot
Install it into your Discord server through Discord's official flow.
04
Use the server and wipe commands
/server, /wipe, /wipes, /findwipe, /population and /map need no clan.
05
Join or create a Rustexa clan
Clan Operations lives on your Rustexa group.
Open
06
Use /operation
Respond Going / Maybe / Not going, answer ready checks and pick up tasks.
07
Leadership pins /operationboard
One live wipe room per operation and channel.

Security & privacy

The smallest footprint that works

Rustexa asks for three permissions and one intent. That is the whole surface.

Permissions requested

View Channel — Read the channel you point a dashboard or alert at
Send Messages — Post command replies, dashboards and alerts
Embed Links — Render Rustexa intelligence embeds

Gateway intents: Guilds only. No Message Content, Presence or Server Members.

No message content
The bot connects with the Guilds intent only. It cannot read your messages — no message scraping, no logging of conversations.
No presence, no voice
Rustexa does not read your Discord online status or voice activity, and never uses them to mark you Going or Ready.
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.
No mass pings
Alerts post with mentions disabled. The bot never uses @everyone or @here.
Separate permission systems
Discord permissions and Rustexa clan permissions are separate. Being a Discord Administrator grants no Rustexa clan authority.

Not available

What the bot deliberately does not do

No dates, no teasers. If a capability is not documented on this page, treat it as unavailable.

Discord presence tracking
Voice channel attendance
Temporary voice rooms
Mass Rust team invites
Rust+ integration
Live roster or player-location commands
AI question answering in Discord
Predictive wipe scoring

Add Rustexa to your Discord

Free, read-only where it reads, and permission-checked where it writes. Public commands work the moment it joins; link your account to track servers, receive alerts and run operations.

Add Rustexa to Discord FAQ