Tags
Creators
Details
1.3
Compatibility
Changes
ClearDropsPlus 1.3 - Smart Entity Cleanup Update
ClearDropsPlus 1.3 adds a new smart entity cleanup system and improves protection for custom items and player-owned entities.
Added
- Added Smart Entity Cleanup for animals and mobs
- Added separate global timed entity cleanup
- Added optional chunk-load entity cleanup
- Added per-group entity limits for farms and mob-heavy chunks
- Added separate animal limits for cows, pigs, chickens and sheep
- Added entity protection for named, tamed, leashed and saddled entities
- Added protection for villagers with professions
- Added protection for named villagers and named iron golems
- Added
/cd entityscanto inspect entity groups in the current chunk - Added
/cd entityclearto clean entity overflow in the current chunk - Added custom item protection for names, lore, CustomModelData and PersistentDataContainer items
Changed
- Entity cleanup is now separated from item cleanup
- Item cleanup and entity cleanup can use different timers
- Entity cleanup only scans already loaded chunks and never force-loads chunks
- Messages now visually separate item cleanup and entity cleanup
- Entity cleanup messages now show nearby block coordinates and chunk coordinates
Improved
- Better protection for custom items
- Better admin tools for checking farms and crowded chunks
- More readable config structure for entity cleanup
- More control over low-end server performance
Notes
The material blacklist still only applies to dropped items by material type.
Custom item protection is configured in config.yml under item-protection.
It is recommended to back up your old config before updating and compare it with the new default config.
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:7amW4bnC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:F7Enqq5q:7amW4bnC"
}

