Tags
Creators
Details
All versions
0.12.0
Beta
Clayium Unofficial: 0.12.011 months ago 47
Compatibility
Minecraft: Java Edition
1.12.2
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Changes
ModularUI is updated to v3.0.4
What's Changed
Added
- Add Integration Recipes by @bqc0n in https://github.com/TRCDevelopers/Clayium/pull/388
- Added Integrations recipes for:
- AppliedEnergistics
- EnderIO
- ExtremeReactors
- Galacticraft
- GregTech
- Mekanism
- Metallurgy
- Sakura
- ProjectRed
- Tinkers' Construct
- Thermal
- TofuCraft
- And some miscellaneous recipes
- Added Integrations recipes for:
- Update ModularUI to 3.0.4 by @bqc0n in https://github.com/TRCDevelopers/Clayium/pull/391
Fixed
- Fix Material Unification (Prefer Clayium Items) by @bqc0n in https://github.com/TRCDevelopers/Clayium/pull/366
- Fix (un)zipping Industrial Clay was possible using Crafting Grid by @bqc0n in https://github.com/TRCDevelopers/Clayium/pull/367
- Fix Item Collector face texture by @bqc0n in https://github.com/TRCDevelopers/Clayium/pull/368
- Fix Pure Antimatter textures by @bqc0n in https://github.com/TRCDevelopers/Clayium/pull/369
- Fix metaitem z fighting by @bqc0n in https://github.com/TRCDevelopers/Clayium/pull/371
- Rework ClayWorkTable GUI by @bqc0n in https://github.com/TRCDevelopers/Clayium/pull/374
- Fix GL Error Invalid Enum by @bqc0n in https://github.com/TRCDevelopers/Clayium/pull/377
- Fix material amount inconsistency with GT by @bqc0n in https://github.com/TRCDevelopers/Clayium/pull/393
Full Changelog: https://github.com/TRCDevelopers/Clayium/compare/v0.11.0...v0.12.1
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Supplementary resources
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:m5ogv9xL:AOU152UI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:m5ogv9xL:AOU152UI"
}

