Tags
Creators
Details
Licensed MIT
Published last year
Updated last month
All versions
0.0.6
Release
0.0.6+1.20.111 months ago 97
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
[1.20.1-0.0.6] - 2025-11-22
Added
- 3D Item Rendering for Copper Chests and Copper Golem Statues in inventory, hand, and item frames
- Copper Chest Oxidation through 4 stages (Copper → Exposed → Weathered → Oxidized)
- Copper Chest weathering mechanics: scraping with axe removes oxidation stages
- Copper Chest waxing with honeycomb prevents oxidation
- Waxed Copper Chests (4 variants) that prevent oxidation, craftable with honeycomb
- Waxed Copper Chest dewaxing with axe
- Copper Button oxidation, scraping, and waxing support
- Copper Golem Statue Oxidation through 4 stages
- Copper Golem Statue scraping and waxing support
- Waxed Copper Golem Statues (4 variants), craftable with honeycomb, still revivable with axe
- Waxed Copper Golem Statue dewaxing with axe (statue remains revivable)
- Double Chest Oxidation Sync to prevent separation
- Double Chest atomic updates to prevent separation during oxidation
- Item preservation during chest oxidation - items no longer drop or duplicate
- Durability damage for axes when scraping/dewaxing (2x for double chests)
- Interaction System for honeycomb waxing and axe scraping with particles and sounds
WeatheringHelperutility class with vanilla oxidation probability (0.05688889)
Fixed
- Copper Golem become_statue sound now uses existing block sounds
- Copper Golem now drops held items when turning into statue
- Waxed Copper Chests and Statues now appear in Creative Mode tab
- Waxed Copper Chests now render with correct copper textures
- Chests no longer oxidize while open (prevents item loss)
- Chests no longer accept scraping/waxing while open
- Double chest oxidation now updates both halves simultaneously
- Particles and sounds now appear on both halves of double chests
- Chest opening with axe/honeycomb after full descraping/dewaxing
- Statue revival with axe prioritizes scraping/dewaxing over revival when applicable
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:a1llHwl4:88wrxCim"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:a1llHwl4:88wrxCim"
}

