Tags
Creators
Details
2.3.4+1.21.1
Compatibility
Changes
Fixed
/inventorywizardon its own now sorts your inventory like/iwiz; before, only/inventorywizard <subcommand>worked.- Default sort: redstone parts (repeaters, comparators, pistons, hoppers, levers, buttons, doors, rails) and decorations (carpets, banners, candles, lanterns, flowers, heads) now get their own categories instead of being lumped in with other blocks. In the client mod, crops you can eat (carrots, potatoes, berries) now sort with food.
- Paper: waxed copper blocks are no longer sorted as tools.
- A settings file that can't be read (for example after a typo while editing it by hand) is now kept as
inventorywizard.json.bakbefore the defaults replace it, so your settings aren't lost.
Downloads
Pick the jar for your Minecraft version and loader. From 26.1 one jar covers Fabric, Quilt, NeoForge and Forge;
before that, NeoForge and Forge share a jar and Fabric/Quilt has its own. Fabric and Quilt also need
Fabric API. The Paper jar runs on Paper and Spigot 1.21 and newer:
InventoryWizard-paper-2.3.4.jar.
| Minecraft | Jars |
|---|---|
[1.21,1.21.1] |
InventoryWizard-fabric-2.3.4+1.21.1.jarInventoryWizard-neoforge_forge-2.3.4+1.21.1.jar |
[1.21.2,1.21.3] |
InventoryWizard-fabric-2.3.4+1.21.3.jarInventoryWizard-neoforge_forge-2.3.4+1.21.3.jar |
[1.21.4] |
InventoryWizard-fabric-2.3.4+1.21.4.jarInventoryWizard-neoforge_forge-2.3.4+1.21.4.jar |
[1.21.5] |
InventoryWizard-fabric-2.3.4+1.21.5.jarInventoryWizard-neoforge_forge-2.3.4+1.21.5.jar |
[1.21.6,1.21.8] |
InventoryWizard-fabric-2.3.4+1.21.8.jarInventoryWizard-neoforge_forge-2.3.4+1.21.8.jar |
[1.21.9,1.21.10] |
InventoryWizard-fabric-2.3.4+1.21.10.jarInventoryWizard-neoforge_forge-2.3.4+1.21.10.jar |
[1.21.11] |
InventoryWizard-fabric-2.3.4+1.21.11.jarInventoryWizard-neoforge_forge-2.3.4+1.21.11.jar |
[26.1,26.1.2] |
InventoryWizard-neoforge_forge_fabric-2.3.4+26.1.2.jar |
[26.2,26.3) |
InventoryWizard-neoforge_forge_fabric-2.3.4+26.2.jar |
[26.3,26.4) |
InventoryWizard-neoforge_forge_fabric-2.3.4+26.3.jar |
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:cU0ynk3p:tUUszaas"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cU0ynk3p:tUUszaas"
}

