All versions
1.5
Alpha
WorldReset 1.55 months ago 43
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Changelog - WorldReset v1.5
β¨ New Features
- π World Templates Loader: Place your custom maps into
WorldReset_Templates/. The plugin automatically detects singleplayer format, converts dimension folders, prevents UUID conflicts, and loads them safely. Supports relative and absolute custom template paths. - πΎ Records Database & Highscores: Built-in
records.ymldatabase tracks attempts, completions, PBs, and average times. Manages a server-wide Top 10 Leaderboard. - π Native Scoreboard Integration: Real-time synchronization with 38 native scoreboard objectives (PBs, records, active players, seed, world name, etc.) completely out of the box.
- π§© PlaceholderAPI Support: Dynamically registers 28 placeholders for timer states, seeds, active filters, and top leaderboards.
- π Block & Item Stopwatch Goals: Stopwatch can now stop on block breaking (
BLOCK) or item collection (ITEM), with automatic registry-based TAB autocompletion.
π New Commands
- π§Ή
/wr filter clear: Instantly clears all structure/biome spawn filters. - βοΈ
/wr timer <enable/disable>: Turns the speedrun stopwatch system ON/OFF. - π Overhauled Help Menu: Redesigned and fully localized in-game command usage instructions (
/wr).
π Fixed Bugs & Optimizations
- π¬οΈ Windows File Lock Fix: Solved the Java world folder locking issue (
session.lock/ region files) on Windows systems. - πͺ Safe Portal Travel: Fixed dimension coordinate math in portals to prevent player suffocation in netherrack or falling in lava.
- π Portal Entity Support: Non-player entities, items, and Ender Pearls now pass through portal dimensions cleanly.
- βοΈ Difficulty Path Fix: Corrected server difficulty reading path from
server.properties.
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:etQu0Jb8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xfwMgINI:etQu0Jb8"
}

