Tags
Creators
Details
Licensed ARR
Published last year
Updated 2 months ago
All versions
2.5
Release
World-Aware Enforcement & Activity Trackinglast year 233
Compatibility
Minecraft: Java Edition
1.21–1.21.10
1.20.x
1.19.x
1.18.x
1.17.x
1.16.5
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
LagXpert v2.5 - World-Aware Enforcement & Activity Tracking
🚀 Highlights
- Per-world enforcement: Mob spawns, storage placement checks and automated scans now honour world-specific overrides, keeping creative hubs relaxed and survival worlds strict.
- Config-driven grace periods: The item cleaner reads
broken-block-tracking(default + material overrides) directly fromitemcleaner.yml, making temporary drop protection fully customisable. - Chunk safeguards from config: Smart chunk management now loads the important-block list from
chunks.yml, so mission-critical structures stay loaded without code changes.
⚙️ Technical Improvements
- Hooked chunk activity tracking into block/entity/player events and scheduled periodic cleanup to keep telemetry fresh.
- Added Folia/Bukkit-safe activity cleanup task and listener to populate
ChunkManager’s analytics in real time. - Introduced world-aware limit providers across listeners, smart mob manager and the auto chunk scanner.
- Implemented configurable alert skipping when no players are online, aligned with
monitoring.yml.
🛠 Developer Notes
ConfigManagerexposes per-world getters and broken block tracking settings;RecentlyBrokenBlocksTracker.configure(...)keeps runtime state in sync.- Added
ChunkActivityListenerandChunkActivityCleanupTaskto the lifecycle; ensure they remain registered when extending the chunk management module.
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:OTUlZl53"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZWFZS4vu:OTUlZl53"
}

