
Better Furnaces & Chests
Enhance your world with tiered furnaces for lightning-fast smelting and massive tiered chests featuring a modern scrollable GUI with built-in sorting, stacking, and searching functionality. Fully configurable and performance-optimized.
Tags
Creators
Details
1.1.0
Compatibility
Changes
1.1.0
- Added Upgrade Kits: Iron, Gold, Diamond, and Netherite.
- Right-click any chest or furnace with the corresponding kit to instantly upgrade it.
- All inventory and properties (Facing, Waterlogged state) are preserved.
- Chest Remodeling:
- Completely new 14x14x14 chest models to match vanilla proportions.
- Separated Base and Lid models for smoother animations.
- Custom VoxelShapes (collision boxes) for both Single and Double chests.
- Double Chest Support:
- Adjacent chests of the same tier and orientation now automatically merge into Double Chests.
- Shared Inventory: Open a double chest to access all 54/108/144/216 slots at once.
- Synchronized Animations: Opening one half triggers the animation and sound for both.
- Preserved Connections: Upgrading a vanilla double chest to Iron now correctly preserves the connection.
- Visual Improvements:
- Upgrade Kits now have unique 3D models in hand and inventory.
- Resolved z-fighting and texture issues on chest lids.
- Customizable Chest Titles:
- Click any chest's name in the GUI to rename it instantly.
- Smart Sync: Custom names are automatically synchronized between both halves when forming a Double Chest.
- Kit Compatible: Upgrading a renamed chest with an Upgrade Kit now correctly preserves its custom name.
- GUI & Search Refinements:
- The chest title and its background are now hidden when searching to avoid visual clutter.
- The title background stays visible during renaming for better focus, while the text is hidden to prevent overlap.
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:VY8NnMTO:C9od7wlL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VY8NnMTO:C9od7wlL"
}
