Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published last month
All versions
3.2.0+mc1.21.11
Release
InvSearch 3.2.0 for Minecraft 1.21.11last month 5
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Client and server
Required content
Changes
InvSort now handles bundles more predictably while sorting.
- Bundles in the selected sortable inventory or container space are moved to the front first.
- Non-bundle items are then compacted, restacked, and sorted behind the bundles.
- Bundle contents are still left alone; this only treats bundle stacks as opaque items so they no longer disrupt the rest of the sort.
- InvSort also avoids treating crafting-like screens as sortable containers.
- Right-clicking an InvSort Sort button now opens an in-game rules screen.
- The rules screen supports custom category order, optional specific item order, protected slots that sorting will not move out of or into, and item-specific slots for chosen item ids.
- The rules screen now uses a more compact layout, keeps its controls inside scaled Minecraft viewports, and supports Ctrl-click plus Shift-click multi-selection for applying slot rules.
- InvSort rules save locally and can be set globally for the player inventory, globally for containers, or as a specific container/screen override.
- InvSearch and InvCatalogue now save their tracking data more defensively, with backup recovery if a local data file is interrupted or malformed.
- InvSearch batches player-inventory history saves during rapid inventory changes, reducing avoidable disk writes during busy sessions.
- Multiplayer world-profile confirmation now uses remappable keybindings instead of hard-coded Enter and Backspace handling.
- Fixed a Minecraft 1.21.11 launch crash caused by the new remappable world-profile keybinding compatibility path.
- InvCatalogue now includes
/inventorycatalogue reports, an in-game browser for saved catalogue reports grouped by world/profile, with item icons, readable counts, selected-item details, and search filtering. - Existing plain-text catalogue report files remain visible in the new browser, and opening the report browser from chat now survives the chat screen closing.
- The InvCatalogue report browser has a darker, more modern Minecraft-style
layout with slot-style item tiles, cleaner report details, contained scrolling
for the selected-item sidebar, better grid clipping, compact
K/M/Bitem-grid counts, and exact selected-item counts in the sidebar. - All three menus now share one cohesive, modern dark look with a colour per mod: gold for InvSort, blue for InvSearch, and green for InvCatalogue. No more mismatched grey panels.
- The InvSort rules screen is split into clear
SlotsandOrdertabs, with an obvious scope selector, a live selection panel with a Protected / Item-slot legend, and hover tooltips that explain what each button does. - InvSearch results are now clean cards that show whether you are holding an item or have only tracked it elsewhere, and expanding a result lists its known locations in a tidy panel. The tracked-world picker matches the new look, shows when each saved world was last used, and marks the active one.
- The InvCatalogue browser groups saved reports under per-world headers, and the report detail view adds a quick bar showing how much of the report each selected item makes up.
- Minecraft 26.x builds now use the same refreshed InvSort, InvSearch, tracked-world, and InvCatalogue screens as the 1.x builds.
- InvSearch and the InvCatalogue report browser now support
:categoryfilters such as:wood,:stone,:tools,:gear, and:storage. - Category filters now keep redstone items out of
:stoneand make:redstonepick up redstone dust plus redstone mechanisms more reliably. - The tracked-world picker now only scrolls its saved-world list when the mouse is actually over that list.
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:wIOLlhbN:EpRVszCi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wIOLlhbN:EpRVszCi"
}

