How to Configure Automatic Wipes on your Rust Server

Rust is a game that encourages resetting the world and player data from time to time to keep things fresh. Many server owners may wish to configure an automatic wipe task for their servers which can wipe all map data, blueprint data, or both on a scheduled interval.

Fortunately, Shockbyte offers functionality for server owners to configure automatic map, blueprint, or full wipes on their Rust servers.


Configuring Scheduled Wipes

To configure an automatic Rust wipe, you will need to create a new scheduled task on your control panel.

  1. Access your control panel.
  2. Navigate to Advanced > Scheduled Tasks.
    Navigate to Advanced > Scheduled Tasks
  3. Click New Task.
    Click New Task
  4. Give your scheduled task a Name.
    Give your scheduled task a Name.
  5. Set the Scheduled Time to when you'd like the wipe to first occur (UTC time zone).
  6. Enable the Interval option, and set the amount of time between each wipe.
  7. In the Command field, select your desired wipe type.
  8. Click Create.

Congratulations, you have now successfully configured an automatic wipe schedule for your Shockbyte Rust server.

If you require any further assistance, please contact our support at: https://shockbyte.com/billing/submitticket.php

Mitchell Smith

Managing Director @ Shockbyte

  • 3 Users Found This Useful
Was this answer helpful?

Related Articles

How to Ban or Unban a Player on Your Rust Server

The ability to ban is built into every Rust server out of the box, preventing unwanted players...

Rust Admin Commands List

Here is a list of all commands for Rust. Note: Some commands listed here may only work with an...

How to Add a Custom Map to Your Rust Server

If you want to use custom maps on your Rust server, you'll need to use the RustEdit Oxide...

How to Set a Server Name for Your Rust Server

When connecting to your server in Rust or viewing the server in the Steam server list, all...

How to Use Rust Oxides Permission System

This guide is designed to help you understand Oxide's permission system. It will cover the basics...