All versions
1.0.0
Release
Timber Chests 1.0.03 months ago 15
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Client and server
Changes
Timber Chests 1.0.0
The first release of Timber Chests introduces matching wooden storage for every non-oak Minecraft wood family.
Added
- Added regular chest variants for all eleven non-oak wood families.
- Added matching trapped chest variants.
- Added unique single and double-chest appearances.
- Added eleven matching wooden chest minecart variants.
- Updated all existing non-oak chest boats with matching chest appearances.
- Updated the Bamboo Chest Raft with a matching Bamboo Chest.
Crafting
- Matching sets of planks now create their corresponding wooden chest.
- Oak planks continue to create the vanilla Chest.
- Mixed or unsupported tagged planks create the vanilla Chest.
- Each custom regular chest can be converted into its matching trapped chest using a Tripwire Hook.
- Chest boat and raft recipes now require the matching regular chest variant.
- Chest minecart recipes now require the matching regular chest variant.
Behavior
- Custom chests retain vanilla-equivalent storage, animations, sounds, obstruction rules, automation support, redstone behavior, and inventory persistence.
- Wooden chest minecarts retain vanilla minecart behavior.
- Chest minecart wood variants persist after saving and reloading.
- Added correct chest minecart item drops.
- Added dispenser support for all wooden chest minecart variants.
Compatibility
- Added a general tag for wooden chests.
- Added a tag for trapped wooden chests.
- Added a regular-only wooden chest tag for recipes that must not accept trapped chests.
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:UZEqRLjD:W0R8xRxI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UZEqRLjD:W0R8xRxI"
}

