2.1.0.1
Compatibility
Changes
ClearLag 2.1.0.1
Multiversion support
- Added native builds for:
- Forge 1.6.4
- Forge 1.7.10
- Forge 1.8.9
- Forge 1.12.2
- Forge 1.16.5
- Forge 1.18.2
- Forge 1.20.1
- NeoForge 1.21.11
- Preserved configurable item and mob cleanup, countdown warnings, operator commands, live JSON policies, saved-mob protection, and spawn-control rules across supported versions.
- The admin spawn-control tool now defaults to disabled, allowing ClearLag to remain properly server-only by default.
- Existing configurations that explicitly enable the tool are preserved.
- Reloading unchanged item-cleanup settings no longer restarts the active cleanup countdown.
- Improved per-version packaging, metadata, archive validation, and Java compatibility checks.
Improved legacy entity clearing
On Minecraft 1.6.4 through 1.12.2, the manual entity-clear command has been redesigned as a proper administrator removal tool.
/clearlag clear entities
/clearlag clear entities Slime
/clearlag clear entities Zombie Skeleton
The existing command spelling remains supported:
/clearlag entities clear
Manual clearing now correctly handles living entities that were previously missed, including:
- Slimes
- Villagers
- Golems
- Animals
- Hostile mobs
- Modded living entities
Manual removal is intentionally separate from scheduled cleanup rules. It can remove bosses and named, tamed, or persistent mobs when explicitly invoked by an administrator.
Players, armor stands, dropped items, projectiles, and nonliving utility entities are excluded.
Specific entity types can now be targeted directly:
- 1.6.4–1.8.9 use their native legacy registry names, such as
Slime. - 1.12.2 uses namespaced IDs such as
minecraft:slime. - Multiple entity types can be requested in one command.
- Invalid entity IDs are rejected before anything is removed.
Modern command behavior
On Minecraft 1.16.5 and newer, /clearlag clear entities is deprecated and will not remove entities.
Modern Minecraft already provides more powerful vanilla entity selectors through commands such as:
/kill @e[type=minecraft:slime]
ClearLag will instead direct administrators toward vanilla /kill selectors.
This only affects the manual entity-clear command. Automatic mob cleanup, item cleanup, countdown warnings, spawn prevention, and other ClearLag systems continue to function normally.
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:zUY503Ar:Wlyunbp0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zUY503Ar:Wlyunbp0"
}

