Tags
Creators
Details
1.2
Compatibility
Changes
ClearDropsPlus 1.2
This update improves usability, configuration handling, admin tools, and overall plugin maintenance.
Added
- Added automatic update checking through Modrinth
- Added console update notifications when a newer version is available
- Added in-game admin update notifications on join
- Added a clickable Modrinth link in the in-game update message
- Added
/cd infocommand to quickly view plugin and config information - Added tab completion for
/cdcommands - Added version fields for:
config.ymlmessages.ymlblacklist.yml
Improved
- Improved automatic config updating for existing installations
- Missing keys in
config.yml,messages.yml, andblacklist.ymlare now added automatically on startup or reload - Existing user settings are preserved during updates
- Improved
/cd helpso players only see commands they are allowed to use - Improved
/cd statusand/cd statsoutput for better readability - Improved global clear world statistics so they now reflect actually removed items
- Improved notification handling with more configurable options
- Improved debug throttling for chunk queue and chunk scan logging
- Improved reload behavior so update checking is refreshed after
/cd reload
Changed
- Reworked notification settings for:
- warnings before clear
- global clear start
- global clear finish
- low TPS stop message
- Updated internal handling for YAML merging and version checks
- Cleaned up runtime state resets during reload and shutdown
Fixed
- Fixed missing command suggestions by adding tab completion
- Fixed inaccurate global per-world clear counts
- Fixed several reload/update edge cases with cached state
- Fixed permission visibility issues in command help output
Notes
This version is fully compatible with existing ClearDropsPlus installations.
If you already have a plugin folder from an older version, you can simply replace the .jar file.
Missing config and message keys will be added automatically without overwriting your existing settings.
- Bukkit compatibility is not officially tested
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:F7Enqq5q:fuL5A1vN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:F7Enqq5q:fuL5A1vN"
}

