All versions
1.3.0
Release
π WorldResetter v1.3.0 Performance & Compatibility Update4 months ago 11
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Changes
β¨ New Commands
| Feature | Command | Description |
|---|---|---|
| π₯οΈ View distance | /wr settings viewdistance <2-32|default> |
Overrides the server's view distance for this world only (Paper-only) |
| π Simulation distance | /wr settings simulationdistance <2-32|default> |
Overrides the server's simulation distance for this world only (Paper-only) |
| ποΈ Structure generation toggle | /wr settings structures <true|false> |
Enables or disables village/stronghold/etc. generation for faster chunk gen |
Info and reset commands (/wr settings info, /wr settings reset) now also report and clear these new performance settings.
π Bug Fixes & Improvements
- Faster world deletion on startup β Deleting the old
worldfolder now happens in parallel across CPU cores instead of one file at a time, cutting boot delay noticeably on large worlds (especially on SSD/NVMe)
β οΈ Compatibility Change
- WorldResetter now targets Paper and Paper-based forks (e.g. Purpur) only β it is no longer compatible with vanilla Spigot or CraftBukkit, since the new view/simulation distance features rely on Paper-exclusive APIs
- Recommended Paper version bumped to 1.21.11+
β οΈ Known Issues
world-typesetting is still under maintenance β Paper does not yet support setting world type at runtime via this method; the/wr settings worldtypecommand shows a maintenance notice and will be re-enabled in a future update
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:AD4Evpot:Qc4aJRot"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AD4Evpot:Qc4aJRot"
}

