Tags
Creators
Details
1.0-Snapshot-3-Patch
Compatibility
Changes
π§ Fixes & Improvements
-
Config merging β New keys from the default config.yml are now merged into the server file on startup or /cl reload without overwriting user settings.
-
Command wiring β All subcommands now go through /clearlite (or /cl), with proper tab completion for worlds, radius values, and member commands.
-
Reload command β /cl reload now updates defaults correctly instead of leaving configs outdated.
-
Task reuse β A single ClearTask instance is used across the plugin, making /cl status and run tracking accurate.
-
Startup safety β More robust command registration and interval handling for low-TPS auto-clears.
Optional dependencies
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:E6waw8p4:MfGLwltP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:E6waw8p4:MfGLwltP"
}

