ResourceWorldResetter

## ResourceWorldResetter 5.2.0 Typed world and network evacuation, configuration isolation, complete localization, and safer asynchronous resets. ### Highlights - Evacuate players to the default overworld, loaded local worlds, named Velocity/BungeeCord backend servers, or destinations registered by add-ons through API 5.2.0. - Discover proxy destinations through the BungeeCord-compatible `GetServers` channel and verify that players actually leave before regeneration begins. - Configure destination types, targets, and bounded transfer timeouts through `/rwr gui`. - Move GUI-managed worlds and teleport overrides to `managed-worlds.yml`, with automatic import from combined version 5 configurations. - Localize commands, notifications, GUIs, history, status values, and teleport outcomes in English, Simplified Chinese, Japanese, and Korean. - Deliver MiniMessage components through a bundled, relocated Adventure platform bridge on Spigot/CraftBukkit and native Adventure on Paper/Purpur/Folia. - Harden Folia scheduling, teleport admission, locale fallback, update reloads, and post-regeneration state restoration. ### Proxy setup  Velocity requires `bungee-plugin-message-channel = true`. The configured destination target must exactly match a backend key in the proxy configuration. RWR sends a transfer request and then waits for actual departure; a plugin message alone is not treated as success. No separate proxy-side RWR plugin is required. ### Upgrade notes Back up the complete RWR data folder and managed worlds before replacing the JAR. Existing combined version 5 world definitions are imported into `managed-worlds.yml`. If upgrading customized messages from `messages.yml`, copy them into the selected `locales/<locale>.yml`. Install exactly one artifact: - `RWR-Spigot-5.2.0.jar` for Spigot/CraftBukkit with Multiverse-Core 5.8.0+. - `RWR-Paper-Folia-5.2.0.jar` for Paper/Purpur/Folia with Worlds 4.4.0+. See the [full release notes](https://github.com/TamaWish/ResourceWorldResetter/blob/2d705bcc74d24645419399bab9ae201a26563503/RELEASE_NOTES.md), [changelog](https://github.com/TamaWish/ResourceWorldResetter/blob/2d705bcc74d24645419399bab9ae201a26563503/CHANGELOG.md), and [evacuation setup guide](https://github.com/TamaWish/ResourceWorldResetter/blob/2d705bcc74d24645419399bab9ae201a26563503/docs/public/EVACUATION.md).

## ResourceWorldResetter 5.2.0 Typed world and network evacuation, configuration isolation, complete localization, and safer asynchronous resets. ### Highlights - Evacuate players to the default overworld, loaded local worlds, named Velocity/BungeeCord backend servers, or destinations registered by add-ons through API 5.2.0. - Discover proxy destinations through the BungeeCord-compatible `GetServers` channel and verify that players actually leave before regeneration begins. - Configure destination types, targets, and bounded transfer timeouts through `/rwr gui`. - Move GUI-managed worlds and teleport overrides to `managed-worlds.yml`, with automatic import from combined version 5 configurations. - Localize commands, notifications, GUIs, history, status values, and teleport outcomes in English, Simplified Chinese, Japanese, and Korean. - Deliver MiniMessage components through a bundled, relocated Adventure platform bridge on Spigot/CraftBukkit and native Adventure on Paper/Purpur/Folia. - Harden Folia scheduling, teleport admission, locale fallback, update reloads, and post-regeneration state restoration. ### Proxy setup  Velocity requires `bungee-plugin-message-channel = true`. The configured destination target must exactly match a backend key in the proxy configuration. RWR sends a transfer request and then waits for actual departure; a plugin message alone is not treated as success. No separate proxy-side RWR plugin is required. ### Upgrade notes Back up the complete RWR data folder and managed worlds before replacing the JAR. Existing combined version 5 world definitions are imported into `managed-worlds.yml`. If upgrading customized messages from `messages.yml`, copy them into the selected `locales/<locale>.yml`. Install exactly one artifact: - `RWR-Spigot-5.2.0.jar` for Spigot/CraftBukkit with Multiverse-Core 5.8.0+. - `RWR-Paper-Folia-5.2.0.jar` for Paper/Purpur/Folia with Worlds 4.4.0+. See the [full release notes](https://github.com/TamaWish/ResourceWorldResetter/blob/2d705bcc74d24645419399bab9ae201a26563503/RELEASE_NOTES.md), [changelog](https://github.com/TamaWish/ResourceWorldResetter/blob/2d705bcc74d24645419399bab9ae201a26563503/CHANGELOG.md), and [evacuation setup guide](https://github.com/TamaWish/ResourceWorldResetter/blob/2d705bcc74d24645419399bab9ae201a26563503/docs/public/EVACUATION.md).

This prerelease introduces GUI-managed world definitions, complete localization, transactional locale/configuration reloads, safer reset lifecycle handling, and dedicated Spigot and Paper/Folia builds. ## Highlights - Moves managed worlds and teleport overrides into `managed-worlds.yml`, with automatic import from an existing combined v5 configuration. - Adds bundled `en_US`, `zh_CN`, `ja_JP`, and `ko_KR` locales with English fallback for missing keys. - Reloads configuration, locale, schedules, and update-checker settings together through `/rwr reload` or the administration GUI. - Prevents incoming RWR teleports from racing into worlds that are evacuating or regenerating. - Avoids duplicate terminal messages for manually started resets. - Hardens reset completion, schedule reconciliation, startup recovery, provider failures, and canonical world identity handling. ## Compatibility - Spigot/CraftBukkit: Java 21+, Minecraft 1.21.4+, Multiverse-Core 5.8.0+; use `RWR-Spigot-5.2.0-beta.1.jar`. - Paper/Purpur/Folia: Java 25+, Minecraft 26.1.2+, Worlds 4.4.0+; use `RWR-Paper-Folia-5.2.0-beta.1.jar`. - Install exactly one RWR platform JAR. The shared core and API adapter are already bundled. ## Upgrade notice Stop the server and back up the complete RWR plugin data folder and every managed world before upgrading. Existing `messages.yml` customizations must be moved into `locales/<locale>.yml`. Review the generated templates and supervise the first reset after upgrading. ### Before replacing the JAR The YAML layout has changed in this release. Replacing the JAR alone does **not** update YAML files that already exist in the plugin data folder, so an existing installation may not receive the new `locale` setting, `locales/` files, or `managed-worlds.yml` layout automatically. Before upgrading, stop the server and make a restorable backup of the entire RWR plugin data folder. Then choose whichever migration approach you are comfortable with: - Keep the existing folder, compare it with the new templates, and manually transfer your worlds, schedules, teleport settings, and customized messages into the new YAML layout. On first successful v5.2.0-beta.1 startup, worlds and teleport overrides already stored in a combined v5 `config.yml` are imported into `managed-worlds.yml` automatically. - Or, after confirming the backup is usable, remove the RWR plugin data folder and start the server once so the new JAR can generate fresh files. Manually copy only the settings and message text you still need from the backup. Do not delete the data folder without a verified backup. If upgrading from `messages.yml`, copy customized text into the selected `locales/<locale>.yml`; the old message file is no longer loaded. After selecting a non-English locale, run `/rwr reload` once so that language file is written under `locales/` if it is not already present.

This prerelease introduces GUI-managed world definitions, complete localization, transactional locale/configuration reloads, safer reset lifecycle handling, and dedicated Spigot and Paper/Folia builds. ## Highlights - Moves managed worlds and teleport overrides into `managed-worlds.yml`, with automatic import from an existing combined v5 configuration. - Adds bundled `en_US`, `zh_CN`, `ja_JP`, and `ko_KR` locales with English fallback for missing keys. - Reloads configuration, locale, schedules, and update-checker settings together through `/rwr reload` or the administration GUI. - Prevents incoming RWR teleports from racing into worlds that are evacuating or regenerating. - Avoids duplicate terminal messages for manually started resets. - Hardens reset completion, schedule reconciliation, startup recovery, provider failures, and canonical world identity handling. ## Compatibility - Spigot/CraftBukkit: Java 21+, Minecraft 1.21.4+, Multiverse-Core 5.8.0+; use `RWR-Spigot-5.2.0-beta.1.jar`. - Paper/Purpur/Folia: Java 25+, Minecraft 26.1.2+, Worlds 4.4.0+; use `RWR-Paper-Folia-5.2.0-beta.1.jar`. - Install exactly one RWR platform JAR. The shared core and API adapter are already bundled. ## Upgrade notice Stop the server and back up the complete RWR plugin data folder and every managed world before upgrading. Existing `messages.yml` customizations must be moved into `locales/<locale>.yml`. Review the generated templates and supervise the first reset after upgrading. ### Before replacing the JAR The YAML layout has changed in this release. Replacing the JAR alone does **not** update YAML files that already exist in the plugin data folder, so an existing installation may not receive the new `locale` setting, `locales/` files, or `managed-worlds.yml` layout automatically. Before upgrading, stop the server and make a restorable backup of the entire RWR plugin data folder. Then choose whichever migration approach you are comfortable with: - Keep the existing folder, compare it with the new templates, and manually transfer your worlds, schedules, teleport settings, and customized messages into the new YAML layout. On first successful v5.2.0-beta.1 startup, worlds and teleport overrides already stored in a combined v5 `config.yml` are imported into `managed-worlds.yml` automatically. - Or, after confirming the backup is usable, remove the RWR plugin data folder and start the server once so the new JAR can generate fresh files. Manually copy only the settings and message text you still need from the backup. Do not delete the data folder without a verified backup. If upgrading from `messages.yml`, copy customized text into the selected `locales/<locale>.yml`; the old message file is no longer loaded. After selecting a non-English locale, run `/rwr reload` once so that language file is written under `locales/` if it is not already present.

# ResourceWorldResetter 5.1.0 ResourceWorldResetter 5.1.0 lays the foundation for upcoming RWR add-ons by introducing a public integration API and matching scheduled warning events, while further hardening reset, scheduler, and shutdown behavior. ## Choose the correct download - **Spigot / CraftBukkit:** `RWR-Spigot-5.1.0.jar` — requires Java 21+ and Multiverse-Core 5.8.0+. - **Paper / Purpur / Folia:** `RWR-Paper-Folia-5.1.0.jar` — requires Java 25+ and Worlds by TheNextLvl 4.4.0+. Install exactly one platform JAR. The shared core and public API are included; do not install separate core or API JARs. ## What is new - Added a stable read-only integration service for compatible add-ons. - Added scheduled warning, cancellable pre-reset, and terminal post-reset integration events across both platform builds. - Improved cleanup and schedule handling after exceptional reset completion. - Isolated third-party listener failures from reset cleanup and player warnings. - Hardened configuration loading, recovery, Folia callback handling, and shutdown behavior. ## Before upgrading Back up the RWR data folder and managed resource worlds, replace the existing RWR JAR while the server is stopped, and perform a full restart. Version 5.1.0 retains the v5 configuration format. ## Anonymous metrics RWR uses bStats for anonymous usage metrics. World names and player identities are not collected. To opt out, set `enabled: false` in `plugins/bStats/config.yml`. Full operator guidance is available in the [Operations and Migration guide](https://github.com/TamaWish/ResourceWorldResetter/blob/v5.1.0/docs/public/OPERATIONS_AND_MIGRATION.md).

# ResourceWorldResetter 5.1.0 ResourceWorldResetter 5.1.0 lays the foundation for upcoming RWR add-ons by introducing a public integration API and matching scheduled warning events, while further hardening reset, scheduler, and shutdown behavior. ## Choose the correct download - **Spigot / CraftBukkit:** `RWR-Spigot-5.1.0.jar` — requires Java 21+ and Multiverse-Core 5.8.0+. - **Paper / Purpur / Folia:** `RWR-Paper-Folia-5.1.0.jar` — requires Java 25+ and Worlds by TheNextLvl 4.4.0+. Install exactly one platform JAR. The shared core and public API are included; do not install separate core or API JARs. ## What is new - Added a stable read-only integration service for compatible add-ons. - Added scheduled warning, cancellable pre-reset, and terminal post-reset integration events across both platform builds. - Improved cleanup and schedule handling after exceptional reset completion. - Isolated third-party listener failures from reset cleanup and player warnings. - Hardened configuration loading, recovery, Folia callback handling, and shutdown behavior. ## Before upgrading Back up the RWR data folder and managed resource worlds, replace the existing RWR JAR while the server is stopped, and perform a full restart. Version 5.1.0 retains the v5 configuration format. ## Anonymous metrics RWR uses bStats for anonymous usage metrics. World names and player identities are not collected. To opt out, set `enabled: false` in `plugins/bStats/config.yml`. Full operator guidance is available in the [Operations and Migration guide](https://github.com/TamaWish/ResourceWorldResetter/blob/v5.1.0/docs/public/OPERATIONS_AND_MIGRATION.md).

Same changelog detail [HERE](https://modrinth.com/plugin/resourceworldresetter/version/5.0.0)

<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/9RhO29M5yuI" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe> Public release history for ResourceWorldResetter. Versions 4.2.1 and earlier are the **legacy v4 line**. Version 5 begins the split-platform architecture and requires a manual configuration migration. ## 5.0.0 — Split-platform release ### Added - Separate production artifacts: - `RWR-Spigot-5.0.0.jar` for Spigot/CraftBukkit with Multiverse-Core 5.8.0+. - `RWR-Paper-Folia-5.0.0.jar` for Paper/Purpur/Folia with Worlds by TheNextLvl 4.4.0+. - Shared `rwr-core` reset coordinator, packaged inside both platform artifacts. - Stable world IDs, unified display names, and explicit platform world-provider identities. - Daily, weekly, monthly, and interval schedules with timezone-aware next-run calculations. - Whole-minute warning configuration and configurable countdown broadcasts. - Reset phases for precheck, evacuation, regeneration, verification, completion, failure, and interrupted recovery. - Persistent reset history and active-operation journaling. - Admin dashboard, world configuration, global settings, teleport administration, history, and confirmation screens. - Player teleport GUI with pagination, permissions, player counts, locked visibility, and reset-phase protection. - Cancellable pre-reset and terminal post-reset API events. - MiniMessage messages and relocated bStats integration. ### Changed - RWR delegates the authoritative lifecycle operation to the selected world plugin. It does not own a direct unload/delete/create pipeline. - Paper/Purpur/Folia now use Worlds by TheNextLvl and do not use Multiverse-Core. - Spigot/CraftBukkit continue to use Multiverse-Core through the dedicated Spigot artifact. - `display-name` is the single presentation name used by chat, logs, notifications, status, history, and GUIs. - Warning values are stored as `warning-minutes`; sub-minute legacy warnings are not supported. ### Fixed - Paper reset deadlock caused by waiting for asynchronous teleports on the primary/global scheduler. - Folia global-region watchdog stalls caused by blocking on entity-region teleport futures. - Folia evacuation is now fully asynchronous; regeneration begins only after teleport completion and a remaining-player check. - Paper/Folia player GUI, teleport, command-completion, and administrator notification callbacks now run on the owning entity scheduler. - Paper/Folia Worlds regeneration now applies same, fixed, and random seed policies and honors level-configuration, gamerule, and world-border preservation settings. - Safe automatic failures now use the configured retry delay and maximum retry count; ambiguous and interrupted outcomes remain unscheduled for operator review. - Schedule listeners now refresh after lifecycle reconciliation changes. - Teleport overrides whose world names contain dots now round-trip through YAML without being split into nested paths. - Paper/Folia startup now rejects missing, unparseable, or older-than-4.4.0 Worlds installations. - Paper/Folia history and status output no longer labels the Worlds provider as Multiverse. - Spigot command output, reset countdown broadcasts, and server-log messages now use native Bukkit delivery and remain visible. - Paper/Folia reset and teleport GUI paths no longer synchronously wait on platform futures. ### Commands - `/rwr status [id]` is the single command for current phase and next-schedule information. ### Migration warning v4 configuration is not loaded automatically by v5. Back up the server, install exactly one matching platform artifact, and migrate values into a fresh `config-version: 5` configuration. See [Operations & Migration](docs/public/OPERATIONS_AND_MIGRATION.md).

# ResourceWorldResetter 4.2.1 ## Paper/Spigot 26.2 Support & Configuration Fix ResourceWorldResetter 4.2.1 combines the 4.2.0 compatibility update with an important configuration persistence fix. ### Added / Improved * **Paper/Spigot 26.2 support** * Updated for Minecraft server platforms targeting 26.2. * No known breaking API changes from 26.1. * Existing commands and configuration remain compatible. * **Code quality improvements** * Internal cleanup and refactoring. * No user-facing command or configuration changes. ### Fixed * **Configuration changes now persist correctly** * Fixed an issue where settings changed through the GUI or commands could appear to work during the current server session but were lost after restarting the server. * Fixed configuration changes being lost after `/rwr reload`. * Configuration reads and writes now use the active Bukkit/Paper configuration instance correctly. ### Upgrade Notes 1. Back up your `plugins/ResourceWorldResetter/` folder and managed resource worlds. 2. Replace your existing ResourceWorldResetter JAR with **v4.2.1**. 3. Restart your server. 4. If upgrading from an earlier version, run `/rwr reset dry-run` before your next scheduled reset. 5. Verify your configuration with `/rwr status` and `/rwr next`. ### Compatibility * **Minecraft:** 26.2 * **Server:** Paper / Spigot * **Multiverse-Core:** Supported * **Configuration:** Existing configurations remain compatible **Recommended:** All users running 4.2.0 should upgrade to 4.2.1.

## ResourceWorldResetter v4.1.1 — QoL, Safety Gates, Operator Tooling, and Paper 26.1 World Folder Fix ### ResourceWorldResetter v4.1.1 includes everything from v4.1.0 plus a Paper 26.1 compatibility fix for world-folder resolution. **What’s included from v4.1.0** - Safety-first preflight gates for TPS, player count, and free disk space with per-gate onFail behavior: delay, abort, or force. - Dry-run resets with /rwr reset dry-run to validate reset workflows without mutating worlds. - Operator tooling with /rwr history and improved /rwr status reporting. - Configurable multi-interval warning broadcasts and player-facing strings moved into messages.yml. - Admin GUI improvements, safer teleport-target configuration, and ongoing logging/reliability improvements. - No breaking changes to v4.0 configuration or command structure. **What’s new in v4.1.1** - Added a shared world-folder resolver so disk checks and delete actions target the real on-disk world folder on Paper 26.1. - Resolves Paper dimension-backed layouts correctly, including world/dimensions/minecraft/resource/ style folders. - Avoids Windows false positives caused by checking a missing server/<worldName>/ path. - reset deletion and history snapshots now use the same safe resolver path. - Delete safety now blocks Paper multi-dimension save roots while still allowing classic standalone worlds and dimension folders. - Added tests for Paper 26.1 resource discovery, overworld mapping, legacy layouts, and delete safety. **Upgrade notes** 1. Stop the server. 2. Back up plugins/ResourceWorldResetter/ and any resource worlds you manage. 3. Replace the plugin JAR with the v4.1.1 release build. 4. If you run Paper 26.1 or later, run /rwr reset dry-run before the next scheduled reset. 5. Restart the server and verify /rwr status and /rwr next. **Support** - Official downloads: [GitHub Releases](https://github.com/TamaWish/ResourceWorldResetter/releases), [Spigot](https://www.spigotmc.org/resources/resourceworldresetter.119878/), [Hangar](https://hangar.papermc.io/Lozaine/ResourceWorldResetter), [Bukkit Dev](https://dev.bukkit.org/projects/resourceworldresetter), and [CurseForge](https://legacy.curseforge.com/minecraft/bukkit-plugins/resourceworldresetter)