Wipe day: the Rust admin's guide to surviving the weekly launch

Rust servers reset on a cycle (weekly, biweekly, or monthly, with the whole ecosystem sharing a monthly forced-wipe rhythm around the game's update schedule), and the reset is the great equalizer that brings everyone back at once: your regulars racing for spawn, returning players checking the new map, fresh players trying the server for the first time, and, inevitably, banned players and cheaters returning on new accounts precisely because day one is when detection is hardest and the damage is greatest. Population peaks, emotions peak, and every kind of moderation load peaks with them, on a schedule you know in advance. That last part is the gift: wipe day is the rare crisis you can fully prepare for.

Half of wipe-day support load is one question: "when is wipe?" Kill it with repetition: the schedule pinned in announcements, in the server info channel, in the Discord's channel topic, and posted again the day before with a countdown. State the timezone every single time. If your wipe ever moves (update delays happen), announce the change everywhere at once, because the players who show up to a wiped server they thought had one more day are tomorrow's angriest tickets.

The first evening of a wipe is your server's weekly rush hour, so schedule it like one: know which staff are on for the first hours, have your most experienced mod on the ticket queue (wipe-night cheating reports need fast, calm triage), and give whoever is in-game playing a break from Discord duty (a mod mid-raid is not reading reports). If your team is small, the honest play is narrowing the promise: announce that non-urgent tickets get answered tomorrow, and hold the line. A published triage order (cheating with evidence first, harassment second, everything else queued) beats heroically drowning.

Wipe day is when ban evaders and cheaters return, because fresh wipes mean fresh accounts everywhere and nobody stands out. Blunt it structurally: account-age gates on your Discord (a day-old Discord account joining on wipe morning is a signal), membership screening on, and in-game, whatever anti-cheat and account-standards your hosting stack supports. In the Discord, this is where member history pays off: a returning troublemaker's behavior pattern is recognizable even on a new name, if anything is actually tracking patterns (our Rust Discord playbook covers the accusation-ticket discipline that keeps wipe-night reports sane).

That pattern-tracking is also where our AI moderator Staffd earns its spot on wipe night (disclosure: we make it): it watches the whole spike without fatigue, knows your server's normal from every previous wipe, remembers member histories, and flags the real problems (the pile-on forming, the scam link in the chaos, the "new" member behaving exactly like last month's ban) to your staff while they handle the queue. The spike stops being the night your moderation goes dark.

The best wipe-day teams close the loop: a short staff debrief after every wipe (what spiked, which tickets repeated, what broke), one improvement shipped before the next cycle, and the decision log updated while memory is fresh. Wipe day comes back every week; a team that improves it by five percent per cycle has a fundamentally different job within a season. The cycle that burns most teams out is the same cycle that lets a disciplined one compound.