Tags
Creators
Details
Licensed ARR
Published last year
Updated 2 months ago
All versions
2.2
Release
Major Features Addedlast year 36
Compatibility
Minecraft: Java Edition
1.21–1.21.5
1.20.x
1.19.x
1.18.x
1.17.x
1.16.5
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
📋 LagXpert Free - Changelog
[2.2] - 2025-01-19
🚀 Major Features Added
- Smart Mob Management System: Automatically removes excess mobs while protecting important entities
- Protects named mobs, tamed animals, equipped entities, and plugin-created mobs
- Intelligent priority system (farm animals removed before valuable entities)
- Performance-optimized gradual removal (max 10 mobs per chunk per tick)
- Chunk processing cooldowns to prevent lag spikes
- Comprehensive notifications with detailed statistics
🌐 Multi-Platform Support
- Platform Detection: Automatically detects Folia, Paper, Spigot, or Bukkit
- Folia Compatibility: Native support with RegionScheduler and AsyncScheduler
- Cross-Platform Scheduling: Intelligent scheduler wrapper for optimal performance
- Backward Compatibility: Seamless fallback to Bukkit scheduler when needed
🎮 Bedrock Edition Support
- Player Detection: Automatic identification of Bedrock players via Geyser/Floodgate
- GUI Optimization: Bedrock-specific inventory layouts and material handling
- Cross-Platform GUIs: Separate templates for Java and Bedrock players
- Smart Fallbacks: Chat-based alternatives when GUIs aren't compatible
🔧 Performance Enhancements
- Zero-Lag Design: All new systems designed to improve performance, not hinder it
- Intelligent Caching: Platform detection and player type caching for optimal performance
- Batch Processing: Operations grouped to minimize server load
- Region-Based Processing: Folia optimization for distributed chunk processing
📊 Enhanced Monitoring
- Advanced Statistics: Detailed tracking of mob removals, protections, and performance
- Platform Reporting: Comprehensive platform detection and capability reporting
- Migration Tracking: Automatic configuration version tracking and migration status
⚙️ Configuration System Improvements
- Automatic Migration: Seamless upgrade from v2.1.x with automatic backup creation
- New Configuration Sections: Platform detection, Bedrock compatibility, smart mob management
- Enhanced Documentation: Comprehensive inline documentation for all new features
- Backward Compatibility: Preserves all existing settings during migration
🛡️ Entity Protection Enhancements
- Advanced Protection Logic: Multiple layers of entity protection with priority systems
- Plugin Integration: Detects and protects entities created by other plugins
- Metadata Awareness: Respects custom entity metadata and flags
- Configuration Flexibility: Granular control over protection rules
🎯 User Experience Improvements
- Intelligent Notifications: Detailed feedback about optimization actions taken
- Cross-Platform Commands: All commands work seamlessly across Java and Bedrock
- Enhanced Debugging: Comprehensive logging and debugging options for troubleshooting
- Progressive Enhancement: Features gracefully degrade based on available platform capabilities
🔄 API Enhancements
- New API Methods: SmartMobManager integration for external plugins
- Platform Detection API: Allows other plugins to detect server platform
- Bedrock Player API: Utilities for detecting and handling Bedrock players
- Enhanced Events: Additional context and information in existing events
📋 Migration & Compatibility
- Automatic Configuration Migration: Seamless upgrade from any v2.1.x version
- Backup Creation: Automatic backup of old configurations with timestamps
- Zero Downtime: Migration occurs during plugin startup with no service interruption
- Rollback Support: Easy restoration from automatically created backups
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:5m7QN80m"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZWFZS4vu:5m7QN80m"
}

