Install ResourceWorldResetter

Download RWR from Modrinth

Before you start

Back up the server, the RWR plugin data folder, and every world you plan to reset. Replace plugin JARs only while the server is stopped; plugin hot-reload tools are not supported.

Spigot / CraftBukkit

1. Install Multiverse-Core 5.8.0 or newer and confirm your resource worlds are registered there.
2. Put RWR-Spigot-5.2.0.jar in plugins/.
3. Remove any Paper/Folia RWR artifact and restart the server fully.
4. Open /rwr gui or edit plugins/ResourceWorldResetter/config.yml.
5. Use the plain world name reported by Multiverse-Core, then check it with /rwr status <id>.

Requires Java 21 or newer.

Paper, Purpur, or Folia

1. Install Worlds by TheNextLvl 4.4.0 or newer and confirm your resource dimensions are registered there.
2. Put RWR-Paper-Folia-5.2.0.jar in plugins/.
3. Remove the Spigot RWR artifact and restart the server fully.
4. Open /rwr gui or edit plugins/ResourceWorldResetter-Paper-Folia/config.yml.
5. Use the Worlds key detected by RWR, such as worlds:resource, then check it with /rwr status <id>.

Requires Java 25 or newer because Worlds 4.4.0+ requires it.

Use one platform build

Do not install both RWR JARs. Paper, Purpur, and Folia use Worlds—not Multiverse-Core—and rwr-core is already bundled inside the platform JAR.

Configure your first resource world

Admin GUI

Run /rwr gui, add a managed world, choose its schedule and evacuation destination, then save. This is the easiest route for a first installation.

config.yml

worlds:
  resource:
    multiverse-world: resource
    display-name: Resource World
    enabled: true
    managed: true
    schedule:
      type: DAILY
      time: "03:00"
    warning-minutes: [30, 10, 5, 1]
    regeneration:
      seed-policy: RANDOM
      keep-world-config: true
      keep-gamerules: true
      keep-world-border: true
    evacuation:
      enabled: true
      destination: world

Run /rwr reload after editing and fix every validation message before continuing.

Run a supervised reset

1. Confirm the evacuation world is loaded and safe.
2. Run /rwr status and /rwr history 10.
3. Start /rwr reset <world-id> while you can watch the console and join the server.
4. Confirm players are evacuated, the provider regenerates the correct world, verification completes, and history records success.
5. Only then rely on unattended schedules.

Continue with configuration or read the complete operations and migration runbook.