Automated Rust Server Wipe Scheduling
Set it and forget it.
Wipe schedules that handle player warnings, pre-wipe backups, blueprint wipes and seed changes, so you never have to wipe a Rust server by hand again.
5 Schedule Types
Weekly, monthly, specific dates, Facepunch forced wipe days (first Thursday of the month), or Wipe now. Mix several schedules on one server.
Pre-Wipe Automation
Take a backup and update plugins before the wipe, and warn players in chat with a countdown. A pending wipe countdown can be cancelled from the panel.
Seed Control
Keep the current seed, use a new random seed, set a custom seed, or load a custom map from a URL. The panel shows Generating map while the new map is built.
Map wipes and blueprint wipes, independently
Each schedule can perform a map-only wipe (players keep their blueprints) or a full wipe (map + blueprints). A common setup is weekly map wipes with monthly blueprint wipes. Panelra handles both with separate schedules on the same server.
Forced wipe handling built in
Facepunch forces a wipe on the first Thursday of every month. Panelra tracks this automatically. Enable forced wipe handling and your server wipes on force day, with optional blueprint wipe and game update included. Smart skip logic prevents double-wipes if your regular schedule overlaps.
Player warnings before every wipe
Choose how long players are warned before a wipe starts: 5, 15, 30 or 60 minutes. Players see chat messages counting down to the wipe so they have time to prepare. If you change your mind, cancel the pending wipe from the panel before the countdown ends.
Smart skip logic prevents accidents
Panelra can skip a scheduled wipe if the server was already wiped within a configurable number of hours. It can also skip regular wipes if a forced wipe is coming within a set number of days. No more accidental double-wipes or wipes the day before force day.
Full audit trail
Every wipe, scheduled or manual, is logged in the automation history with timestamps, duration, trigger type (scheduled, manual, forced), and status (completed, failed, skipped with reason). See exactly what happened and when.