Links
Tags
Creators
Details
Licensed MIT
Published last month
Updated 3 weeks ago
All versions
3.11.9.1
Release
Tinker's Continuum 3.11.9.1last month 23
Compatibility
Minecraft: Java Edition
26.1.x
Platform
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Changes
Continuum Construct 26.1.2-3.11.9.1
Fixes
- Fixed a crash when Continuum Construct was loaded without JEI installed.
- JEI integration now stays optional and only hooks recipe sync when JEI is present.
Compatibility
- Updated the required Continuum Core dependency to 1.11.6.
- Built against NeoForge 26.1.2.109.
Continuum Construct 26.1.2-3.11.9
New
- Added AllTheModium family material compatibility for Allthemodium, Vibranium, and Unobtainium.
- Added molten fluids, melting recipes, casting recipes, material stats, traits, and generated tool textures for the three main AllTheModium metals.
- AllTheModium materials are made through smeltery casting only; Part Builder recipes are intentionally disabled for these materials.
Improvements
- Updated AllTheModium material colors so Continuum tools better match the original AllTheModium tool palette.
- Added matching harvest tiers for Allthemodium, Vibranium, and Unobtainium harvest tools.
Fixes
- Fixed cleaver/severing drops copying early-loaded recipe outputs with temporary direct item holders, which could spam NBT predicate warnings after pickup.
- Fixed AllTheModium ores refusing to break even when Continuum tools displayed the correct harvest tier.
- Added vanilla tool component syncing so mods that check DataComponents.TOOL can recognize Continuum harvest tools correctly.
- Fixed older Continuum tools missing the new vanilla tool component after loading an existing world.
- Fixed a crash caused by trying to create registry lookups after Minecraft registries were already frozen.
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:e0tUZE5Y:CZg5tYVW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:e0tUZE5Y:CZg5tYVW"
}

