Links
Tags
Creators
Details
Licensed MIT
Published last month
Updated 3 weeks ago
All versions
3.11.4
Release
Tinker's Continuum 3.11.42 months ago 24
Compatibility
Minecraft: Java Edition
26.1.x
Platform
NeoForge
Supported environments
Client and server
Changes
Tinkers' Continuum 26.1.2-3.11.4
Compatibility
- Added material and tool part compatibility for AE2, Advanced AE, ExtendedAE, Ender IO, Powah, and Jade.
- Added item-only armor part recipes for supported compat materials so armor pieces can be crafted consistently.
- Added world loot integration for generated Tinkers' tools with more controlled modifier pools.
- Added Apotheosis and Apothic Enchanting support for higher modifier caps and vanilla-style enchantment conversion where supported.
- Added safer recipe visibility and conditional loading for optional compat content.
Fixes
- Fixed Smeltery recipe sync crashes caused by missing or empty optional tags, including raw steel materials.
- Fixed slime embellishment recipes by restoring the missing TCon slime embellishment tool tag.
- Fixed several JEI recipe display issues for compat materials, casting, and tool part recipes.
- Fixed luck tooltip and enchantment naming so tools show the correct vanilla-style effect such as Fortune, Looting, or Luck of the Sea.
- Fixed tool loot balance so world-generated tools no longer roll too many random modifiers.
- Fixed common structure loot balance so early-game chests no longer hand out too many high-tier Tinkers' tools or materials.
- Fixed Tinker's Anvil and Scorched Anvil variants so they keep their material/texture when broken and placed again.
- Fixed tool part fallback tooltips so missing material/stat IDs render safely.
- Fixed white or missing models for AE2-family compat materials including Certus Quartz, Fluix, Quantum, and Entro.
- Improved Mantle recipe network errors so broken synced recipes report the failing recipe ID.
Version Safety
- Restricted NeoForge compatibility to 26.1.2.78 or newer, below 26.2, so unsupported loader versions fail with a clear dependency message.
- Verified NeoForge 26.1.2.77 is rejected with the expected loader warning.
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:AL2R3vmS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:e0tUZE5Y:AL2R3vmS"
}

