Tags
Creators
Details
2.1
Compatibility
Changes
LagXpert v2.1 - Bug Fixes & Improvements
Critical Bug Fixes
Item Cleaner System:
- Fixed excluded items being deleted despite being in the exclusion list
- Improved item type detection and comparison logic
- Added automatic protection for enchanted items, named items, and items with lore
- Better error handling to prevent crashes with corrupted items
Entity Cleanup System:
- Fixed named entities being removed incorrectly
- Fixed tamed animals being deleted despite protection settings
- Fixed leashed entities being removed when they shouldn't be
- Improved detection of custom names, taming status, and leash connections
- Better respect for all protection configuration options
Configuration System:
- Fixed configuration lists not loading properly from files
- Improved validation to prevent invalid settings
- Added automatic fallback values for missing or empty configurations
- Better error messages when configuration files are missing
Improvements
- Enhanced debug logging for better troubleshooting
- Improved performance with better error handling
- More reliable detection of important entities and items
- Better configuration validation on server startup
⚠️ Important Notes
- Your existing configurations will continue to work
- Excluded items in itemcleaner.yml will now be properly respected
- Protected entities in entitycleanup.yml will now be properly protected
- Enable debug mode in config.yml to see detailed logs if needed
This update focuses on fixing critical issues reported by users. No new features were added to ensure stability.
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:ZWFZS4vu:rr5bJOWs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZWFZS4vu:rr5bJOWs"
}

