Version 5.1.0 · Spigot Java 21+ · Paper/Folia Java 25+

Reset worlds.
Keep control.

Automated resource-world regeneration with safe player evacuation, authoritative provider integration, independent verification, crash history, and operator-first tooling.

rwr / operations

$ /rwr status

world rainforest

phase EVACUATE

players moving safely…

provider Worlds

regenerate completed

identity verified

safe spawn verified

One plugin, two native builds

Use the platform that matches your server

Each artifact integrates with the world provider appropriate for its scheduler model. Install exactly one RWR JAR; shared core is already bundled.

S

Spigot / CraftBukkit

Synchronous Bukkit integration backed by Multiverse-Core’s authoritative regeneration API.

RWR-Spigot-5.1.0.jarMultiverse-Core 5.8.0+
Spigot installation →
F

Paper / Purpur / Folia

Region-aware scheduling and non-blocking evacuation backed by Worlds from TheNextLvl.

RWR-Paper-Folia-5.1.0.jarWorlds 4.4.0+No Multiverse
Paper/Folia installation →

Do not install both builds. Paper/Folia does not use Multiverse-Core, and rwr-core is an internal bundled module—not a server plugin.

Designed for live servers

A controlled reset pipeline

Every operation is observable, guarded, and verified instead of being treated as a blind delete-and-recreate task.

01

Schedule precisely

Daily, weekly, monthly, and interval schedules with timezone-aware next-run calculations and warning minutes.

02

Evacuate safely

Move players to a validated destination and refuse regeneration while anyone remains in the managed world.

03

Delegate correctly

Call Multiverse-Core or Worlds as the authoritative lifecycle provider instead of owning a risky folder pipeline.

04

Verify independently

Check registry, loaded state, world identity, and safe spawn after the provider reports completion.

05

Recover conservatively

Persist active markers and history. Interrupted ambiguous operations are recorded, never silently replayed.

06

Operate visually

Admin and teleport GUIs, status, history, confirmations, permissions, player counts, and reset-phase protection.

Quick start

Go from download to supervised reset

Back up first, choose the correct artifact, and validate the provider relationship before enabling unattended schedules.

Install the provider

Use Multiverse-Core on Spigot, or Worlds on Paper/Purpur/Folia.

Install one RWR build

Place the matching platform JAR in plugins/ and fully restart.

Configure and inspect

Use /rwr gui, then verify the phase and next schedule with /rwr status, plus history.

Run one supervised reset

Confirm evacuation, regeneration, verification, messages, and logs before automation.

Clone the source

The browser uses the normal repository URL. Git clients use the canonical .git endpoint.

git clone https://github.com/TamaWish/ResourceWorldResetter.git

Main operator commands

/rwr help
/rwr status
/rwr history 10
/rwr reset <world-id>
/rwr reload
/rwr gui
/rwr tp

Permissions

NodeDefault
rwr.adminop
rwr.reloadop
rwr.resetop
rwr.statusop
rwr.historyop
rwr.tptrue
rwr.teleport.world.*op

Permission details →