
Pala's Item Clear
Server-side item cleaner that removes dropped items on a timer with colored warnings, powerful filters, and a recovery bin to undo mistakes. A modern, configurable ClearLag alternative for Forge, Fabric, and NeoForge from Minecraft 1.20.1 to 26.2.
Tags
Creators
Details
0.1.2+26.2-neoforge
Compatibility
Changes
Performance and compatibility update for Pala's Item Clear.
Fixed
- Lag spikes during clears on Minecraft 1.21.9 and newer: owner names for the recovery bin now come from online players and the local user cache only, never from a blocking request to Mojang's profile service.
- Items thrown by mobs (piglin bartering, villagers, allays) are no longer treated as player-owned, so
excludePlayerOwnedItemsprotects only items dropped by players. - Minecraft 1.21.5-1.21.8 now have dedicated JARs. The former
1.21.10-fabricJAR could crash there during a clear, and the former Forge and NeoForge JARs did not load at all. - Every JAR now loads on all the Minecraft patches of its band. Forge 1.20.2-1.20.3, 1.21 and 26.1.x, NeoForge 1.20.2-1.20.3, 1.20.5, 1.21 and 26.1.x, and Fabric 26.1.x previously had no loadable JAR.
- Faster recovery-bin deposits for large farm clears.
Added
- Item tags in
filters.excludedItems, for example"#minecraft:logs". filters.minAgeTicksOverridesfor per-item or per-tag minimum ages, for example{"minecraft:wheat_seeds": 1200, "#minecraft:logs": 2400}.
Compatibility
- New artifacts:
1.21.8-fabricand1.21.8-neoforge(Minecraft 1.21.5-1.21.8),1.21.5-forge(Forge 55), and1.21.8-forge(Minecraft 1.21.6-1.21.8, Forge 56-58). - The
1.21.10-*artifacts now cover Minecraft 1.21.9-1.21.10, including Forge 59 and NeoForge 21.9. - Existing configuration files keep working and gain an empty
minAgeTicksOverridesentry on the next load.
Notes
- On Minecraft 1.20.4 NeoForge servers with vanilla clients, use NeoForge 20.4.248 or newer: earlier 20.4 builds cannot open any container for vanilla clients, including the recovery bin.
- To keep only the 30-second warning, set
"warningSeconds": [30]; use[]to disable warnings.
See CHANGELOG.md for the full details.
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:DoKkIPix:FikHK2BU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DoKkIPix:FikHK2BU"
}
