All versions
1.7beta
Beta
WorldReset 1.7beta3 months ago 142
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
Platforms
Bukkit
Paper
Purpur
Changes
Changelog - WorldReset v1.7beta
π New Features & Changes
- π Scoreboard Management: From now on, your plugin scoreboard objectives (like deaths or attempts) are not cleared by default upon world reset! Perfect if you want to preserve your statistics between games.
- βοΈ New
/wr scoreboardCommand: You can easily bring back the classic clearing behavior from previous versions using the/wr scoreboardcommand. It now safely only clearswr_objectives without touching other server scoreboards. - π Status Check: Type
/wr scoreboard statusto see if plugin objectives will be cleared during the next reset. - π New Statistic - Deaths: The plugin now persistently tracks the total number of deaths for every player in
records.yml. You can display it using the newwr_deathsscoreboard objective or the%worldreset_deaths%PlaceholderAPI placeholder! - π Death Limit System: You can now configure the plugin to automatically reset the world if the total number of player deaths in the current run reaches a limit! Use the revamped
/wr death <number>command to set the global pool of shared lives. Great for multiplayer hardcore challenges! Tracks viawr_run_deathsandwr_lives_left. - π§Ή Scoreboard Reset Command: Added a new admin command
/wr scoreboard reset [player]to instantly wipe all permanent speedrun statistics and personal bests from a player's record (or everyone's record). - π Granular Permissions: I have completely rebuilt the permission system! You can now grant your moderators access to specific sub-commands instead of giving them full access to entire modules. For example, give someone
/wr timer startbut prevent them from changing the/wr timer mode!.
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:xfwMgINI:ouHLZGp4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xfwMgINI:ouHLZGp4"
}

