ResourceWorldResetter

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.