Tags
Creators
Details
5.1.0
Compatibility
Required content
Changes
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.
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:bw02lGJo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PjsJlPJ9:bw02lGJo"
}


