How to run a Rust server Discord (the most hostile moderation job in gaming)

Rust is a game about losing things to other people: your base gets raided offline, your teammate takes the loot and leaves, your hours of farming vanish in a doorcamp. The emotional temperature of a Rust Discord reflects that: the salt is constant, the accusations are constant, and the banter is rough by any outside standard. That is not a failure of the community, it is the culture of a game whose whole premise is hostility, and moderating it with a general-audience word list would flag half the server by lunch.

The moderation problem is therefore a precision problem: inside a channel where "you are all garbage and your base was garbage" is normal post-raid banter, you have to spot the message that crossed into something real: the threat aimed at a person instead of a player, the harassment campaign that followed someone from the game, the racial abuse hiding in the noise.

The layout that fits the game's rhythms: announcements (wipe schedule above all, because the wipe cycle is the server's calendar), server info and rules, a general that you accept will run hot, team/clan recruitment (LFG is a Rust Discord's biggest utility), raid clips and screenshots (giving the salt a stage keeps some of it out of general), and a ticket system for the two report types that must never live in public: cheating accusations and player reports. If your server runs any economy or VIP perks, that support gets its own ticket category too.

One Rust-specific rule earns its keep immediately: no accusation threads in public channels. A cheating accusation in general chat becomes a witch hunt in minutes, and half of them are wrong (good players look like cheaters to the players they farm). Evidence goes in a ticket, staff review it, and the verdict is not a community vote.

Rust needs the permissive-norms approach more than almost any community (we wrote about moderating communities with their own culture): write down that post-raid salt, trash talk, and rough banter are normal here, so your moderation never has to pretend the server is something it is not. Then draw the hard lines explicitly: threats or harassment aimed at the real person, hate speech, doxxing, and following someone across platforms to continue a fight. In a rough-culture server, the written line between in-game hostility and real-world hostility IS the rulebook.

Here is what makes Rust moderation genuinely hard: the baseline is so noisy that both humans and filters fail. A volunteer mod skimming general chat tunes out the hostility (they have to, it is constant), which means they also miss the escalation buried in it. A keyword filter is worse than useless: calibrated for a normal server it flags everything; calibrated for Rust it catches nothing.

Context-reading is the only approach that works here, and it is what our AI moderator Staffd does (disclosure: we make it): it learns YOUR server's normal (the register of your general chat, your written norms), tracks member history, and flags the deviations that matter (the banter that turned personal, the newcomer getting piled on, the pattern behind one member's constant "jokes") to your staff with reasoning, human-confirmed. In a community where everything sounds like a violation, the valuable skill is knowing what actually is one.

Rust staff burn out on two things: adjudicating cheating accusations and absorbing abuse from banned players. Protect them structurally: evidence standards for every accusation (no clip, no case), a written ban-appeal process with a cooldown (the furious appeal written at 2am is withdrawn by noon), rotation off the ticket queue, and a hard rule that abuse of staff in tickets ends the ticket. And keep decision logs: Rust players relitigate bans for months, and the server with written records wins every argument. The wipe cycle gives the whole job its rhythm (our wipe-day guide covers the weekly spike in detail).