Tags
Creators
Details
Licensed MIT
Published last month
Updated 4 days ago
All versions
1.21.1-1.5.0-NeoForge
Release
Tinkers Construct (Unofficial port) 1.21.1-1.5.0-NeoForge4 days ago 1,231
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Modern Foundry 1.5.0
Synced with the latest Tinkers' Construct
- Fancy armor stands: bamboo (small), bone (with arms), necrotic bone (glowing) and clear (invisible when dressed)
- Horn material for slimesuit ribcages
- Phantom cuirass
- Reworked Gold Guard and Chrysophilite: bonuses now scale with the gold armor you wear
- Edible tools rework
- Tools with an inventory now drop their contents when destroyed
- Shields can take a banner's patterns without its base color using a sky slime bottle
- New JEI categories: Fuel, Materials and Tool Modification
- Upstream balance changes and bug fixes
Bug fixes
- Melting modifier now properly fills its tank (Blazing Blood from blazes, Milk from skeletons...)
- Part chests and smeltery blocks no longer lose their contents when you relog
- Tree Physics: hand axes, broad axes and mattocks are recognized as axes, and let trees fall naturally (sneak to fell the whole tree the Tinkers way)
- Kama can shear sheep, mooshrooms and snow golems again
- Breaking a casting table or basin now drops the cast
- Create crushed ores can be melted in the melter and smeltery
- Fixed a Crafting Station duplication glitch
- Bows, crossbows and war picks: draw time and loaded ammo work properly, and Modern Foundry arrows are accepted as ammo
- Fixed AOE mining behaving unpredictably with fake players (deployers, etc.)
⚠️ Items already lost to the old part chest bug can't be recovered.
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:3xgZFdrY:74WNtrx7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3xgZFdrY:74WNtrx7"
}

