Tags
Creators
Details
Licensed ARR
Published last year
Updated last week
All versions
1.12.4
Beta
ClearLag++ 1.12.42 months ago 2,534
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Changelogs:
aAdded:
- Every entity ClearLag deletes is now written to the console while debug mode is on, together with the feature that caused it — scheduled clear, manual clear, kill mobs, AI-Optimization, mob spawn limiter, mob stacking, projectile limiter or nuke — plus the entity type, its custom name and its coordinates. Until now the debug output only ever reported what was kept, so a report of "ClearLag removed my mob" could neither be confirmed nor ruled out. If something disappears and no removal line appears for it, ClearLag was not the cause.
- Dropped items are now reported with their actual item type instead of just "item", so they can be matched directly against the excluded items list.
- The reason a mob was spared is now named in the log: whether it survived because it has a custom name, because it is breedable, or because it carries the exclusion tag.
Fixed:
- Mob stacking removed mobs without announcing it, so other plugins were never told and could not prevent the removal, and nothing about it appeared in any log. It now uses the same removal path as every other feature.
- The debug line for a spared mob was easy to mistake for a removal notice — it looked like a deletion but was in fact printed the moment a mob was protected. It now states clearly that the mob was kept.
- Removal messages for AI-Optimization and for item clearing were written before the removal was actually carried out, so they could report removals that never happened.
- The version number reported by the plugin did not match the release it shipped in, which made it impossible to tell from the version alone whether a fix was included.
Removed:
- The separate removal messages for AI-Optimization and for item clearing. Both are replaced by the single unified removal message, which reports the same information in one place. The distance that triggered an AI-Optimization despawn is still included there.
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:7bhTp28M:iivMYrg7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7bhTp28M:iivMYrg7"
}

