Questions, answered honestly

Rustexa is a Rust community platform built around server intelligence: which servers exist, how populated they are, when they wipe and what evidence supports that. It also hosts groups, LFG and clan operations, and delivers alerts about the servers you follow.

The rule behind everything is that Rustexa shows what it can actually support. When something is unknown, it says unknown instead of filling the gap with a guess.

Finding a server to play on by wipe timing, region, type and population. Following servers and getting alerted when they wipe or fill up. Recruiting through groups and LFG. And coordinating a clan's wipe day through operations, participation, ready checks, tasks and assignments.

No, for browsing. Server, wipe, population and map information is public on the website and through the public Discord commands.

You need an account to track servers, receive alerts, join a clan and use clan operations.

No. Everything Rustexa does has a home on the website. Discord is an additional place to read the same canonical information and to act on it with your team.

No. Server intelligence, wipe discovery and tracking work without one. Only Clan Operations — operations, participation, ready checks, tasks, assignments and the live wipe room — needs a Rustexa clan.

Rustexa maintains its own canonical index of Rust servers and observes them directly. Coverage grows over time; if a server is missing from the index, Rustexa will say it has no data rather than invent an entry for it.

Population and status come from Rustexa's own repeated observations of each server, so the values you see carry an observation time. Every surface shows how old a value is instead of implying it is live.

If a server stops answering, Rustexa reports that state honestly rather than repeating the last known number as if it were current.

Because Rustexa refuses to fabricate. A wipe hour with no trustworthy timezone, a map seed nobody published, a population from a server that is not answering — all of these are shown as unknown.

That is a deliberate product decision: an honest gap is more useful than a confident wrong answer.

From direct, repeated observation of the servers themselves, plus schedules published by the organizers who run them. Each value keeps the class of evidence behind it, and the interface tells you which one you are looking at.

No. Only a wipe time supported by qualifying canonical evidence is shown as a confirmed server wipe with an exact countdown. Everything else is labelled as a date only, or as no anchor at all.

Pick how many rockets, C4, satchels or explosive 5.56 you want and Rustexa returns the exact resources to farm: sulfur, charcoal, metal fragments, low grade fuel, cloth, plus the components you cannot farm such as metal pipes, tech trash and rope.

Batch recipes are counted in whole crafts, exactly like the game: gun powder is made ten at a time and explosive 5.56 two at a time, so a partly used batch still costs a full one.

You can also switch to the I have mode: enter what is in your boxes and Rustexa shows the maximum of each explosive you could make and which resource runs out first. Those rows are independent maximums, not a combined plan.

Every recipe is taken from the official Rust wiki and verified by hand. The date the data was last checked is shown on the calculator page. Rustexa does not sync automatically with Facepunch, so if a cost changes in game we update the data and change that date.

The calculator is manual and deterministic. It never reads screenshots, it makes no predictions, and it stores nothing — your loadout only lives in the page address so you can share it.

The Farm Calculator is the only tool available today. Other calculators are on the roadmap and are listed on the tools page as not built yet, without dates.

Four things: look up server, wipe, population and map intelligence; find a server to play on by wipe timing; show and manage the servers you track and the alerts they send; and run clan operations — participation, ready checks, tasks, assignments and a live wipe room.

• /server
• /wipe
• /findwipe
• /tracked
• /operation
• /operationboard

Use the Add to Discord button on the Rustexa Discord bot page and pick the server you want it in. It asks for View Channel, Send Messages and Embed Links — never Administrator.

Only for anything tied to your account. Public lookups work for anyone. Tracking, alerts and every clan action need a linked Discord account so Rustexa knows which Rustexa identity is acting.

Run /alerts in Discord to get a one-time code, then redeem it while signed in to Rustexa.

• /alerts

/server, /wipe, /wipes, /findwipe, /population, /map, /popular, /group, /lfg, /status and /rustexa. /tracked and /alerts need a linked account but no clan.

• /server
• /wipe
• /wipes
• /findwipe
• /population
• /map
• /popular
• /tracked
• /alerts

/operation requires you to be a member of the Rustexa clan that owns the operation.

• /operation

Pinning a live wipe room with /operationboard, opening and closing ready checks, creating and removing assignments, and raising an emergency alert. These use your Rustexa clan permission, not a Discord role.

• /operationboard

Because the two permission systems are separate on purpose. Discord Administrator controls your Discord server. Rustexa clan permissions control your clan's operations.

Rustexa checks the clan role attached to your linked Rustexa identity. If you are not an owner, admin or leader in that clan, the action is refused no matter what your Discord role is.

It searches the canonical wipe feed for a server to play on, filtered by wipe timing, region, server type and minimum players. The reply is private to you and can be refined with buttons instead of retyping the command.

• /findwipe

It shows full intelligence for one server: observed population, region, wipe timing with its evidence label, current map identity and network. Anything unverified is shown as unknown.

• /server

It focuses on one server's wipe history and next wipe, with the evidence label attached to each. It never invents a time that is not supported.

• /wipe

It shows the current observed population and the recent trend for one server. It reports observations; it does not forecast.

• /population

It privately lists the servers on your Rustexa account with their population and wipe timing, and lets you untrack from Discord. The list itself lives on Rustexa.

• /tracked

It opens a private panel for your clan's current or next operation: participation counts, the ready check, tasks, assignments and role coverage — plus your own Going / Maybe / Not going and Ready / Not ready buttons.

If you belong to more than one clan, choose which one with the clan option.

• /operation

It pins one persistent dashboard — the live wipe room — for an operation in the current channel. It shows the operation, server, start, lifecycle state, participation counts, ready-check counts, role gaps and task progress.

Only clan leadership can create it, and asking twice returns the existing dashboard rather than posting another.

• /operationboard

Yes. It redraws from the same canonical operation the website uses whenever that operation changes, and rapid bursts of changes are coalesced into a single refresh. There is also a manual refresh button.

• /operationboard

No. Pressing Going, Ready, or opening tasks and assignments from the dashboard answers you privately. Only the aggregate counts appear on the shared board.

Yes, while a ready check is open, from either /operation or the live wipe room. Your answer is the same canonical answer the website shows.

• /operation

Yes, if you hold the clan permission to update tasks. Tasks can be filtered by Open, Mine, Required and All, and marking one done — or reopening it — updates the same operation the website shows.

• /operation

Yes. Members with the clan readiness permission can create and remove assignments from the /operation panel, and the assignee gets a notification through their own preferences.

• /operation

A manual way for authorized clan leadership to reach the clan immediately with a Defense, Urgent operation or Clan emergency alert, with an optional short reason. Sending one requires confirmation and it goes to the clan's current members through their own notification preferences.

No. Rustexa Emergency Alerts are manually triggered by authorized clan leadership. Rustexa does not detect raids automatically, and automatic raid detection is not something Rustexa is building.

It is the reason Rustexa believes a wipe happened or will happen. A wipe Rustexa observed itself is stronger evidence than a schedule an organizer advertised, and both are shown differently.

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

Because the date is supported but the exact time is not. A published hour with no trustworthy timezone is not an exact time, so Rustexa shows the date and stops there rather than picking an hour for you.

The wipe date is known, but no trustworthy exact time is available. No countdown is shown.

There is no supported time anchor at all — neither a confirmed wipe time nor a planned one — so nothing is presented as a time.

Rustexa is currently observing the wipe on that server, not counting down toward an advertised one.

Rustexa observed the wipe a short time ago, so the server is fresh.

The wipe comes from an advertised or canonical schedule and has not been observed yet. The server may wipe early, late or not at all.

Because it comes from observations taken at intervals, and a server that stops answering produces no new observation. Rustexa shows the age of the value instead of pretending it is live.

Rustexa observes tracked servers continuously and repeatedly through the day. Every value carries its own observation time, which is the number you should trust rather than a global refresh promise.

No. Rustexa reports observed population and its recent trend. It does not forecast.

No. Rustexa shows wipes that were observed and wipes that are scheduled, each labelled. Predictive wipe scoring is not currently available.

A Rustexa group with operations enabled: a roster, roles and a shared place to plan wipe days. It is independent of any Discord server, which is why one clan can be reached from several Discord servers and vice versa.

A planned clan event — most often a wipe day. It carries a lifecycle, an optional link to a canonical server wipe, participation, an optional ready check, tasks, assignments and role coverage.

Owner holds the clan and can transfer it. Admin manages the clan and its operations. Leader can run operations — creating them, opening ready checks and making assignments. Member takes part: responding, answering ready checks and working tasks.

Yes. Gameplay roles such as Pilot or Builder are separate from clan authority, and one member can hold several.

A gameplay role used for role coverage — it tells the clan whether someone who flies is on the operation.

No. Gameplay roles describe what you do in Rust. They grant no clan authority whatsoever.

Each member's answer to the operation: Going, Maybe, Not going, or No response if they have not answered yet.

A short window leadership opens right before an operation to ask who is actually ready now. Answers are Ready, Not ready, or No response. Only one ready check is open on an operation at a time.

No. Going is an intention given in advance. Ready is a separate answer to a ready check happening now.

No. No response means the person has not answered. Rustexa never converts silence into a decision.

No. It means no answer was given. Not ready is an explicit answer someone chose.

The work an operation needs: units of preparation and execution that can be required or optional, assigned or unassigned, open or done. They can be filtered by Open, Mine, Required and All.

A named member given responsibility on an operation. Leadership creates them, and the assignee is notified through their own preferences.

A comparison between the gameplay roles an operation wants and the roles held by members who are taking part — for example Pilot 0 / 1.

No. Coverage says a capable person is present. An assignment says a specific person was given the job. A covered role with nobody assigned is a real and common situation.

The operation's history stays intact — Rustexa does not rewrite what happened. The former member simply loses access and stops counting toward the clan's current roster and recipients.

The persistent operation dashboard leadership pins in a Discord channel with /operationboard. It keeps the whole clan looking at one canonical picture instead of scattered messages.

• /operationboard

Tracked-server alerts (wipe started, wipe soon, schedule changed, population threshold), clan operation assignments, ready-check openings, and manual emergency clan alerts.

You track a server, choose which conditions matter and where they should be delivered. Wipe started fires only from an observed wipe; wipe soon fires from an advertised schedule and is labelled as such.

When leadership assigns you something on an operation, you are told once, through your own preferences.

When leadership opens a ready check, participants are notified so they can answer while it is open.

Manual, leadership-triggered alerts to the clan's current members: Defense, Urgent operation or Clan emergency, with an optional short reason. They are rate limited and always human-initiated.

Yes. Notification preferences are controlled on Rustexa, per family and per channel, and you can pause or delete any alert or unlink Discord entirely.

You set a window in your own timezone. During it, external delivery such as Discord is held back, and daylight-saving changes are handled for you.

Quiet hours suppress the interruption, not the record. The notification still lands in your Rustexa inbox so nothing is lost while you are asleep.

The usual reasons: Discord is not linked, no destination is chosen, the alert family is switched off, quiet hours were active, or the bot cannot post in the chosen channel. The /alerts panel shows the current state of each of these.

• /alerts

It should not be. Each event is recorded once and each delivery is de-duplicated, so a repeated trigger does not turn into repeated pings.

No. No presence inference is used by Discord Clan Operations.

No.

No. Ready is only ever an answer you give.

No. Going is only ever an answer you give.

No. Availability stays private to you and is not exposed through the Discord bot.

No. Nothing about your Discord activity is turned into clan state.

No. Rustexa clan permissions are checked against your linked Rustexa identity and your current role in that clan. Discord roles grant nothing.

So Rustexa knows which account is pressing the button. Linking proves that this Discord user is you, using a one-time code you redeem while signed in to Rustexa. Without it, a Discord id would be just a name in a chat window.

You can unlink at any time.

No. It connects without the message content intent and asks only for View Channel, Send Messages and Embed Links.

Not currently available: Discord presence tracking, voice attendance, temporary voice rooms, mass Rust team invites, a Rust+ integration, live roster or player-location commands, AI question answering, and predictive wipe scoring.

If a capability is not documented on the Discord bot page, treat it as not available.