All versions
1.0+mod
Release
1.010 months ago 3,184
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Fabric
Forge
NeoForge
Quilt
Supported environments
Server-side
Singleplayer
Changes
The initial release of this data pack
~~ Details ~~
- Combining an amethyst crystal with an item by throwing them on top of a smithing table will lower the repair cost of that item by one and consume the amethyst shard. The lower the repair cost is, the more the particles that appear will shift from red to orange to yellow to green to blue, until a puff of white particles appears when the repair cost is at 0.
- Combining a diamond with a trimmed item (an item with a trim component) by throwing them on top of a smithing table will remove the trim (remove the trim component) and consume the diamond.
- Combining an echo shard with a cursed item (an item with either curse of vanishing or curse of binding) by throwing them on top of a smithing table will remove the curses and consume the echo shard. This will also spawn a vex.
- Combining a book with an enchanted item by throwing them on top of a smithing table will transfer the enchantments from the item to the book. The item remains, just unenchanted.
- [1.21.5 and up only] Combining a written book with a feather and an ink sac by throwing them together on top of a smithing table will unsign the book, turning it into a book and quill with the same contents as the written book. The author and title information is lost.
- A config menu is available using
/function gear_tinkering:_config, where each feature can be toggled on or off. Vexes spawning when removing a curse from an item can also be disabled. - An uninstall function (
/function gear_tinkering:_uninstall) is available to delete the scoreboards added by the data pack before uninstalling. - An setup function (
/function gear_tinkering:_setup) is available to reset the data pack to how it would be when it was installed (reenabling all features and showing a data pack installed message in chat)
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:LZIfwEFj:PkArwuCh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LZIfwEFj:PkArwuCh"
}

