Tags
Creators
Details
4.0.0
Compatibility
Changes
A major reset-system upgrade with a brand-new /rwr command tree, phase-aware state tracking, and automatic migration support.
What’s New: New unified /rwr command tree — cleaner, easier to use, and built for the future. Phase-aware reset state — track resets with explicit stages for better visibility and control. Built-in startup migration — upgrading from v3 is smoother, with automatic config migration and backup creation. Improved admin workflow — better help, clearer status output, and more structured management commands.
Highlights: /rwr gui for the main admin interface /rwr reset now for manual resets /rwr status for live reset state /rwr next for upcoming scheduled resets /rwr region for region management tools /rwr help for a built-in command reference
Breaking Changes: Legacy commands such as /rwrgui, /resetworld, /rwrregion, and /rwrresume are no longer registered. The config format has changed for v4, but migration is automatic on startup. Reset state now uses explicit phases for better clarity and future reliability.
Upgrade Notes: Back up your server files before upgrading. Replace the old jar with v4 and restart the server. Check /rwr status after startup to confirm everything migrated correctly. Update permissions, scripts, and command usage to the new /rwr structure.
Why this release matters: ResourceWorldResetter v4 is the foundation for a cleaner, more powerful reset system going forward. It makes the plugin easier to operate, easier to understand, and ready for the next stage of development.
Need help? Run /rwr help in-game for quick usage, or check the included migration docs for the full upgrade path.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:PjsJlPJ9:nledD2Pj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PjsJlPJ9:nledD2Pj"
}

