2.0
Compatibility
Required content
Changes
Expanded Inventory 2.0
Expanded Inventory 2.0 introduces a completely redesigned inventory customization system, persistent personal presets and major compatibility improvements.
Added
- Redesigned full-height inventory control menu
- 12 structured module placement positions
- Freely movable Custom layout mode
- Balanced, All Left and All Right layout presets
- Three personal Save and Load preset slots
- Separate saved layouts for different active module counts
- 12 module color presets and custom color controls
- Movable and colorable 3x3 Crafting Upgrade module
Mshortcut for showing or hiding modules while the inventory is open- JEI, EMI and REI recipe compatibility
Improved
- Personal presets now persist after restarting the game
- All Left and All Right no longer remove saved custom presets
- Presets are stored separately for each player
- Legacy personal preset files are migrated automatically
- Module interaction inside external inventory screens
- Curios inventory layout stability
- Traveler's Backpack and Sophisticated Backpacks compatibility
- Left-click, right-click and drag behavior across module slots
- Belt and upgrade recipes
Fixed
- Presets disappearing when changing belts or active module counts
- Saved layouts being overwritten by another module-count configuration
- Module placement changing after reopening the world
- Custom layouts shifting incorrectly when Curios is opened
- Items being dropped unexpectedly from external inventory screens
- High-stack interactions causing incorrect item counts
- Crafting Upgrade rendering and interaction issues
- Multiple inventory UI overlap problems
Community and Support
Found a bug, have a suggestion, or want to share your inventory layout? Join our Discord community.
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:GxuD4fSk:ogyPElC4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GxuD4fSk:ogyPElC4"
}

