Links
Tags
Creators
Details
Licensed LGPL-3.0-only
Published 4 years ago
Updated 2 years ago
All versions
2.0.0+1.20.1
Release
v2.0.0+1.20.1 Fabric3 years ago 10.1K
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Fabric
Quilt
Supported environments
Client and server
Required content
Any compatible version
Changes
More Chests Changelog
2.0.0 Double Chests Update
Added
- Double Chest variants of:
- All plank chests
- All copper chests
- All wool chests
- Wool Chests
- Custom GUI based on wool color
- All 16 colors
- Can be dyed
- Can be crafted with any wool color
- Bamboo Chest
- Cherry Chest
- Tooltips for all chests showing their upgrade ingredients and what they upgrade into
Changed
- Copper Chests inventory size reduced to 36
- Updated textures for all plank chests
- Updated textures for all copper chests
- Added a shapeless recipe for all plank chests
- Added a sound and particle effect when upgrading a chest
Fixed
- an issue causing signs and item frames to be unable to be placed on chests
- Vignette effect applied twice in chest all GUIs
- Various other bugfixes and improvements
1.0.3
Fixed
- Issue causing items in the outer columns of the netherite chest to drop when picked up.
1.0.2
Fixed
- Issue causing server crash when a chest is opened
- Fixed positioning of player inventory title in wooden and copper chests
1.0.1
Fixed
- Issue causing chests to never close their lid
- Netherite Chests Title changes location based on GUI size
1.0.0
Added
- Oak Chest
- Birch Chest
- Spruce Chest
- Jungle Chest
- Acacia Chest
- Dark Oak Chest
- Mangrove Chest
- Crimson Chest
- Warped Chest
- Copper Chest
- Exposed Copper Chest
- Weathered Copper Chest
- Oxidized Copper Chest
- Waxed Copper Chest
- Waxed Exposed Copper Chest
- Waxed Weathered Copper Chest
- Waxed Oxidized Copper Chest
- Iron Chest
- Gold Chest
- Netherite Chest
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:Du77FavA:AspHKe1p"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Du77FavA:AspHKe1p"
}

