How to Schedule Rust Server Wipes

This guide shows you how to schedule automatic wipes for your Rust server. The Schedules system in the Game Panel lets you reset player data, world files, or perform a full wipe on a recurring schedule — so the wipe happens by itself instead of you having to remember to do it manually. If you're new to wipes, read the How to Wipe a Rust Server guide first to understand the different wipe types.

Step 1: Login and Select Your Server

1. Log in to the NolimitHost Game Panel at https://panel.nolimithost.cc/ using your account credentials
2. Select your Rust server from the server list

Step 2: Open Schedules

1. Click "Schedules" in the left sidebar — this is where you create automated tasks that run on a timer
2. Click "Create Schedule"

Step 3: Configure the Schedule

1. Enter a name for the schedule (example: "Weekly Rust Wipe")
2. Configure the desired timing and frequency (for example, every week on a specific day)
3. Save the schedule

Step 4: Create a Wipe Task

1. Open the newly created schedule
2. Click "Manage"
3. Click "Create Task"
4. Select "Wipe Rust Server Files" from the task list

Step 5: Select a Wipe Type

Choose the wipe type that best matches your server's wipe cycle. Not sure what these do? See the "Types of Wipes" section in the How to Wipe a Rust Server guide.

Blueprint Wipe

• Deletes all player data and blueprints
• Players will need to relearn all blueprints
• Recommended for major progression resets

Map Wipe

• Deletes all world and map files
• Generates a fresh world on the next startup
• Player blueprint progression is retained

Full Wipe

• Deletes both world files and player data
• Provides a completely fresh start for all players
• Commonly used for monthly wipe cycles

Step 6: Save the Task

1. Verify the selected wipe type
2. Click "Create" or "Save"
3. The wipe will now execute according to the schedule configuration

Additional Notes

• Always notify your players before scheduled wipes
• Ensure the server is configured to restart after the wipe if required
• Test new schedules before relying on them for production servers