Tags
Creators
Details
Licensed MIT
Published 2 weeks ago
Updated 2 days ago
All versions
2.3.0-beta.1
Beta
GTCalcBoard 2.3.0-beta.15 days ago 13
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Server-side
Client and server
Changes
[2.3.0-beta.1] - 2026-09-17
Improved
- Added a self-healing background indexing recovery mechanism that safely triggers EMI recipe pre-caching after 40–50 seconds if recipe baking stalls or completion lifecycle events are dropped in large modpacks.
- Improved GTCEu compatibility to deductively recognize custom
GTRecipeTypedefinitions registered by modpacks and third-party addons (such as Cosmic Frontiers'cosmiccore, KubeJS, etc.) via runtime reflection, ensuring all GT-based recipes are natively mapped regardless of namespace. - Promoted the welcome onboarding tutorial seen state to persistent client configurations (
CalcBoardClientConfigandclient_preferences.json), remembering user dismissal across multiple worlds and server logins.
Fixed
- Fixed an overclock calculation issue where recipes requiring 2A or more (e.g. 4A, 8A) would calculate excessive or distorted amperage downscaling when processed in higher voltage tier machines.
- Fixed a critical data loss bug where duplicate
ClientPlayerNetworkEvent.LoggingOutevents upon exiting singleplayer worlds would overwrite valid board saves on disk with an initialized empty board. - Fixed an issue where modpack-specific GTCEu recipes (such as
cosmiccore:mana_leaching_tubandcosmiccore:arcane_crucible) were incorrectly assigned aGeneric Unsupported Processbadge despite having their EU/t and duration parameters extracted correctly. - Fixed an issue where clicking 'Explore on My Own' in the welcome onboarding popup failed to persist the seen state, causing the modal to reappear on every game launch.
Optional dependencies
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:XEVN5V0r"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:beYVVxDr:XEVN5V0r"
}



