Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 4 years ago
Updated 2 months ago
All versions
0.9.32
Beta
GregTech Experimental 0.9.324 years ago 118
Compatibility
Minecraft: Java Edition
1.12.2
Platform
Forge
Supported environments
Client and server
Required content
Unavailable version
Changes
0.9
- 0.9.32 Fix dust crafting recipes
- 0.9.31 Fix wrench tool crafting recipe
- 0.9.30 Setup modrinth publishing
- 0.9.29 Fix centrifuge dustTin recipe input count
- 0.9.28 Fix industrial grinder recipe file name for profiles
- 0.9.27 Fix item valve recipe
- 0.9.26 Fix electrolyzer accepted fluids
- 0.9.25 Fix recipe teblock prefixes
- 0.9.24 Fix thorium fuel rod recipe
- 0.9.23 Show fuel output in JEI
- 0.9.22 Fix secondary output slot in automatic machines
- 0.9.21 Fix energium dust yield
- 0.9.20 Unique TEBlock names
- 0.9.19 Add missing tritium recipe
- 0.9.18 Cleanup
- 0.9.17 Update maven dependency guide
- 0.9.16 Fix publish project properties
- 0.9.15 Fix generic cover textures
Closes #44 - 0.9.14 Fix FusionReactor cast crash
- 0.9.13 Add missing uranium ore grinder recipe
- 0.9.12 Replace GitHub Packages with Su5eD maven
- 0.9.11 Add compressed air cell voiding recipe
- 0.9.10 Fix Sonictron dropping its contents
- 0.9.9 Fix air cell extraction recipe glitch
- 0.9.8 Fix computer cube dropping holo item slots
- 0.9.7 Fix computer cube side sync
- 0.9.6 Client side guidebook translation
- 0.9.5 Remove HardHammer crafting sound
Nope, this just refuses to work - 0.9.4 Fix mortar crushing recipes
Fixes #43 - 0.9.3 Fix crash on empty smelting recipe output
- 0.9.2 Fix energy tier calculation returning negative values
- 0.9.1 Remove CapeHandler
- 0.9.0 CraftTweaker Support
Merge pull request #42 from Su5eD/feature/ct-support
Optional dependencies
Any compatible version
Any compatible version
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:T2cdMYjB:FNiJ1QMy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:T2cdMYjB:FNiJ1QMy"
}

