Tags
Creators
Details
Licensed GPL-3.0-only
Published last year
Updated 7 months ago
All versions
2.0.0
Release
Karta WorldReset 2.0.07 months ago 25
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Changes
[2.0.0] - 2026-03-08
Added
- Cloud Command Framework V2: Completely replaced the old Bukkit command executor logic with Incendo's Cloud Command Framework for faster, type-safe, and intelligent command parsing.
- Dynamic Tab Completion: High-quality tab completion for all commands and arguments, including dynamic suggestions for loaded and tracked world names (
/kwr addworld [world],/kwr removeworld [world]). - Targeted World Resets: Admins can now target a specific world to reset using
/kwr reset [target_world]. It incorporates a robust confirmation system (requires/kwr reset confirmwithin 30 seconds). - New Command Alias: Added
/worldresetas a root command alias alongside/kwr,/kartaworldreset, etc. - MiniMessage Support: Integrated Adventure API's MiniMessage format to replace outdated legacy Bukkit color codes (
&). It now supports rich text, HEX codes, gradients,<click>events, and<hover>text. - Centralized
messages.yml: Extracted all hardcoded string messages, titles, and ActionBars into a unified, customizablemessages.ymlconfiguration file.
Changed
- Refactored backend mechanics in
Reset.javato support single-world resets seamlessly without triggering a global loop. - Removed legacy
Messagesconfiguration block fromconfig.ymlin favor of the new independent file. - Cleaned up the codebase by removing the deprecated
Messages.javaand Bukkit nativeCommands.java.
Fixed
- Fixed command error throwing in console when attempting to reset worlds under Bukkit native commands.
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:teZTbHhK:P2EPCDd5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:teZTbHhK:P2EPCDd5"
}

