Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published last week
All versions
3.3.0+mc1.21.11
Release
InvCatalogue 3.3.0 for Minecraft 1.21.113 weeks ago 2
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Required content
Changes
Inv+ bug fixes and quality-of-life improvements.
- InvCatalogue
includeInventorynow counts your carried inventory from the start of the session and refreshes it when you check status, generate a report, or stop the session. - InvCatalogue inventory-inclusive reports now include equipped armor, offhand items, and any item stack currently held by the cursor.
- Stopping an InvCatalogue session now opens the newly saved report directly in the in-game report browser for review.
- InvSort now handles full inventories more reliably while sorting.
- InvSort can use empty reserved item slots as temporary sorting space when needed, while keeping those reserved-empty slots empty when sorting finishes.
- InvSort, InvSearch, and InvCatalogue now use the same main menu size.
- InvSort hotbar slots are locked by default. Open the rules screen to unlock individual hotbar slots for sorting or assign specific items to them.
- The InvSort rules screen action is now labelled
Assigninstead ofAssign Item. - InvSearch and InvCatalogue now distinguish known component/NBT variants such as enchanted gear, potion variants, custom names, and other data-bearing stacks instead of merging everything into the base item id.
- InvSearch now supports
<variantsearches for known enchanted, potion, and component-backed stacks, such as<silfor Silk Touch. - InvSearch can now optionally be installed on a Fabric server to provide an automatic world/profile hint to clients, while still working client-side only.
- InvSearch menu scroll buttons now sit inside the menu frame.
- Fixed an InvSearch launch crash from duplicate auto-profile packet registration on the client.
- Fixed InvSearch optional-server compatibility for Minecraft 1.20.5, 1.20.6, and the 26.x release lane before release.
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:rV7fRk8Z:S7mTT9Dg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rV7fRk8Z:S7mTT9Dg"
}

