1.0.1
Compatibility
Changes
-
Client-only
Install only on the client. No server installation required. Filter list is stored locally. -
Pickup filter
Filtered items are not picked up (client-side mixin cancels pickup). Works in singleplayer and on servers. -
Auto-drop on servers
On servers without the mod, the server still adds items to your inventory. Filtermos automatically drops filtered items from your hotbar so they don’t stay in your inventory.- Current selected slot is checked every tick and dropped immediately if it’s a filtered item (no slot switching, no visual change).
- Other hotbar slots are checked every 5 ticks when you’re not mining; the mod briefly switches to that slot, sends a drop packet, then switches back at the start of the same tick so the hotbar selection doesn’t visibly change.
-
Mining-friendly
While you’re breaking blocks (isDestroying()), the mod never switches the selected slot. Only the current hand is dropped if it holds a filtered item. This keeps mining (e.g. with a pickaxe) uninterrupted. -
“Looks like never picked up”
Filtered items are hidden in the client’s rendering:- Hotbar / held item: Rendered as empty (Gui mixin).
- Container screens (inventory, chests): Slots containing filtered items are not drawn (AbstractContainerScreen mixin).
So on screen it looks like you never picked those items up.
-
Baritone support
When Baritone is installed (baritonemod id), the mod does not switch hotbar slots to drop from other slots. It only drops from the current selected slot. This avoids conflicting with Baritone’s hotbar use (e.g. tool/block switching). -
Configuration
Open the config UI with G (default) or via Mod Menu → Config. Add/remove items to filter; the list is saved locally.
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:hJGMavuX:nucdyaZd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hJGMavuX:nucdyaZd"
}

