Tags
Creators
Details
5.2.0
Compatibility
Required content
Changes
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
GetServerschannel 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.jarfor Spigot/CraftBukkit with Multiverse-Core 5.8.0+.RWR-Paper-Folia-5.2.0.jarfor Paper/Purpur/Folia with Worlds 4.4.0+.
See the full release notes, changelog, and evacuation setup 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:qToaBuqg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PjsJlPJ9:qToaBuqg"
}

