Tags
Creators
Details
All versions
0.6.0
Beta
TiCEX - Tinkers Construct EX 0.6.05 months ago 3,899
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Fixes
- Requires AddonAPI 2.1.0
- Fixed an issue where MekaWeapons catalysts were not being applied correctly
- Fixed an issue where Reforged SlashBlade kill counts were not being recorded correctly
- Normalized Meka mode changes with Modem modifiers
Changes
- Updated More-Config: Allows adjustment of tools and RF furnace temperature in settings without breaking gameplay
- Added many Modem functions + support for Evolved (Draconic Evolution)
- When remodeling, ProudSoul, Refine, and KillCount are compared between the tool and catalyst, and the larger value is used.
- When Evolved modifications are applied, the tool now deals the corresponding Draconic damage.
- Changed the Reconstruction Core recipe.
- Changed textures for some tools (Thanks, razdo73!)
Additions
- Eternity Modifier (Avaritia Integration): Grants one upgrade, one ability, and one defense slot each. Maximum Lv3.
- DragonForce Modifier (Draconic Evolution Integration): The tool will now deal corresponding Draconic damage. Exclusively for the material properties of Draconium-Chaotic crystals. If Evolved is present, it will deal a higher grade of damage compared to that.
- Added an advancement
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
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:ZDgJ7ogS:azGuLDVP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZDgJ7ogS:azGuLDVP"
}

