Tags
Creators
Details
Licensed MIT
Published 2 months ago
Updated last week
All versions
2.4.3
Release
GregTech Calculator Board 2.4.3last week 114
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client-side
Server-side
Client and server
Changes
[2.4.3] - 2026-10-18
Added
- Added bacteria stat configuration (Production and Metabolism tiers 1-5) to Star Technology Bacterial Hydrocarbon Harvester nodes, allowing flow calculations based on actual breed levels for accurate sugar/biomass consumption and fluid production.
Fixed
- Fixed an issue where an invalid fuel was displayed in the Modular Combustion Frame (MCF), and ensured Rocket Modules correctly offer dedicated rocket fuels (Rocket Fuel, RP-1, Monomethylhydrazine, and Sorbitol Hypergolic Fuel) instead of standard combustion fuels.
- Fixed an issue where auxiliary fluids (such as liquid tungsten disulfide or lubricants) in combustion generators and rocket modules could be duplicated as both core recipe inputs and hardware auxiliary inputs on the node card.
- Fixed an issue where heating coil speed bonuses were applied after overclocking instead of before overclocking, ensuring recipe durations round down after coil speed boosts first and then at each overclock step to match in-game processing times.
- Fixed an issue where running Auto-Ratio from an upstream anchor rounded downstream machines requiring more than 1 machine down instead of up, causing insufficient processing capacity.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
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:beYVVxDr:NCeLT0JT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:beYVVxDr:NCeLT0JT"
}

