Rust Console Wipe Day Checklist: How to Wipe and Keep Players Coming Back

What a wipe actually does on Rust Console

A wipe resets your server so everyone starts fresh, and it helps to know the two kinds before you touch anything. A map wipe rolls a new map and clears every base, box, and tool cupboard, but players keep the blueprints they have already learned. A full wipe, sometimes called a blueprint or BP wipe, does all of that and also resets learned blueprints, so the whole server is back to stone tools and rock-and-torch starts.

One thing to get straight up front: on console there are no add-ons to install and no F1 developer console. The wipe itself happens in your host panel, and everything around it, the announcements, the resets, the rewards, runs through a WebRCON bot. That is the whole toolkit, and it is plenty.

Most owners run a map wipe weekly, commonly Thursday around 18:00 UTC, with a full blueprint wipe less often. Pick a rhythm and hold it. A server left unwiped for more than a month tends to get laggy and unstable as entities pile up, and an inconsistent schedule is one of the fastest ways to lose a returning crowd.

Set the schedule and announce it early

The single biggest retention mistake on console is treating wipe day as a surprise. Your regulars plan their evening around a wipe. If they do not know when it lands, they drift to a server that told them. Lock in a fixed day and time, post it where your community lives, and keep it the same every week so people can plan around it.

Then run a countdown in game. Over WebRCON you can push announcements with the say command, and a bot can schedule them so you are not sitting there typing. A simple cadence works well: a heads-up 24 hours out, a reminder at 1 hour, and a final call at 15 minutes. Those timed announcements do two jobs at once. They warn the people currently building not to waste materials, and they remind everyone the reset is coming so they log back in for it.

How to wipe your Rust Console server, step by step

The wipe happens in your host panel, whether you rent from G-Portal or Nitrado. The exact button names vary a little, but the flow is the same everywhere.

First, decide map wipe or full wipe. A map wipe clears the world and keeps blueprints. A full wipe also resets blueprints, so save those for when you want a true reset and keep weekly wipes map-only. Second, set a new map seed, or change the world size, to force a fresh map. Both push the server onto a brand new layout, and a world size around 3500 to 4500 suits most community servers: big enough to explore, small enough to keep players bumping into each other.

Third, if you have changed any live settings over RCON, things like gather scale, decay, or the PvP toggles, write them to config with server.writecfg before you restart. Convars set live do not survive a reboot on their own, and a wipe is a reboot, so anything you did not write to the config quietly reverts to default. Fourth, save and let the host restart the server. It comes back on the fresh map, empty and ready. That is the entire mechanical job, and it takes a couple of minutes. Everything that decides whether the server is still busy on Saturday happens around it, not in it.

Expect the bot to drop when the server reboots

A wipe is a full server restart, and a restart drops your bot. The connection to the game runs over WebRCON, and when the server reboots that connection breaks until the bot reconnects. The same thing happens whenever G-Portal auto-updates and reboots on a Facepunch patch. If your bot does not come back on its own, your killfeed, announcements, leaderboard, and store delivery all go dark at the exact moment the server is busiest.

This is why reconnection matters more on wipe day than any other day of the week. Look for a bot that reconnects on its own within seconds of the server coming back, so you are not manually restarting anything while a full lobby waits. If yours needs babysitting after every reboot, wipe day is exactly when that weakness costs you players.

Get the fresh map re-listed so players can find it

After a wipe restart your server drops off the community browser for a bit and has to reappear. New or freshly restarted servers can take up to around 15 minutes to show up again, so do not panic if it is missing right after the reboot. Players open the browser with Y on Xbox or Triangle on PlayStation, and if your regulars are searching in that window, tell them to switch on the Show Empty filter so the fresh, empty server still appears.

One setting keeps you findable: your server name needs to stay under about 60 characters or it can be filtered out, with the word players search at the front. Beyond the browser, list your wiped server in a directory so returning players see the new wipe in one place, instead of scrolling thousands of results hoping to spot yours.

The retention layer most owners skip

Here is the part that keeps the server alive on day two. A clean map is not a reason to come back on its own. A fresh competition is. Reset your leaderboard at every wipe so every player starts at zero and the race for the top of the board is wide open again. A fresh leaderboard turns a quiet wipe into a week-long contest, and it costs you nothing to run.

Pair it with a battle pass reset so there is a fresh grind and a ladder of rewards to chase from the first hour. Because nothing gets installed on console, a battle pass is tracked and delivered by a WebRCON bot that watches play and hands out kits in game, and wiping it at reset gives everyone a clean slate to climb. Keep every reward non-combat. Facepunch pushes back hard on pay-to-win, and an August 2025 rule bans granting paid DLC or skins to players who do not own them, so stick to resources, quality-of-life perks, and kits that do not hand out a fighting edge.

Restock your Kit Vending Machines while you are at it, and remember the numbers: the first 24 to 48 hours after a wipe is peak population and peak spend. That is when a fresh leaderboard, a reset battle pass, and stocked kits do the most work, and it is exactly the window where owners who skipped the retention layer watch their server empty out.

Your first 24 to 48 hours playbook

Treat the day after wipe as its own job. An hour or so in, run a launch event to pull people together. event_airdrop or event_helicopter over RCON both work well as a spark. Keep the killfeed flowing and the leaderboard visible so the competition feels live, and check that the bot is actually online, since that is the one thing that quietly breaks everything else if it dropped on the reboot.

Before you step away, post the next wipe time. The moment players know exactly when the server resets again, you have given them a reason to come back, and you have turned a one-night spike into a weekly habit. That single announcement is the difference between a server that is packed every Thursday and one that is dead by the weekend.

Frequently asked questions

Keep reading

reset your battle pass at wipe · start a fresh leaderboard · get your wiped server found · keep the bot online after the reboot · fix a server missing from the community browser