Bukkit

v4.2.1 — 26.2 Support & Code Quality

Problem

On enable, ConfigManager cached a FileConfiguration reference, then ConfigService.loadConfig() called plugin.reloadConfig(), which replaced JavaPlugin's internal config instance. All setters mutated the stale instance while plugin.saveConfig() wrote the new (unchanged) instance to disk. Settings appeared to work in-memory for the current session but were lost on the next boot.

Fix

ConfigManager now resolves configuration through a Supplier (plugin::getConfig in production). Every read/write uses the live FileConfiguration that JavaPlugin.reloadConfig() / saveConfig() share, so GUI and command changes persist across restarts and /rwr reload.

v4.2.0 — Spigot/Paper 26.2 Support & Code Quality

v4.2.0 is a compatibility and code-quality update. No API, config, or command changes, existing setups should carry over as-is.

What's new

• Intended to support Spigot/Paper/Bukkit 26.2 — no known breaking API changes since 26.1 (please report any issues you run into)
• Minor code quality improvements and internal clean-up (no user-facing changes)

Upgrade notes

1. Back up plugins/ResourceWorldResetter/ and any resource worlds you manage.
2. Replace the plugin JAR with v4.2.0.
3. Run /rwr reset dry-run once (recommended) before the next scheduled reset.
4. Verify /rwr status and /rwr next after restart.