Links
Tags
Creators
Details
Licensed MIT
Published 11 months ago
Updated 11 months ago
All versions
1.2
Release
ItemCleaner 1.211 months ago 417
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Server-side
Client and server
Changes
- ✅New Multiple Cleanup List Management System:Supports creating multiple independent cleanup lists (e.g., default list, dedicated cleanup lists, etc.) for flexible switching between scenarios; provides a complete set of management commands:
/cleandrops listmanager create <name>:Create a new list
/cleandrops listmanager switch <name>:Switch current list
/cleandrops listmanager delete <name>:Delete specified list (at least one list remains)
/cleandrops listmanager current:Check currently active list
/cleandrops listmanager all:Display all available lists
/cleandrops listmanager list:View all lists and their included items
- ✅ Admin Item: Admins can obtain the Cleanup Hoe from the creative inventory or by using the command
/give @s itemcleaner:cleanup_hoe. Hold it in hand and right-click to instantly remove all item drops listed in the cleanup configuration. - ✅Enhanced List Management Features:Each list can be independently configured with cleanup items, supporting cross-list rule isolation; new rules are automatically applied when switching lists without restarting the game; currently active list is marked with * when displaying lists for intuitive status distinction
- ✅Optimized Configuration File Structure:Added currentCleanupList field to record the name of the current list; added cleanupLists object to store multiple lists as key-value pairs (keys are list names, values are item ID lists); retained default list (default) and added example list (NowClean) for quick start
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:iPpb3wPz:BFEQRfYd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iPpb3wPz:BFEQRfYd"
}

