1.0.1
Compatibility
Changes
Some bug fixes
~~ Details ~~
-
Fixed a bug where enchantments could be duplicated by transferring an item's enchantments to a stack of more than one book. (thanks to ozir on PMC for reporting this bug!)
- This is fixed by making it so that only stacks of one item can be affected by tinkering recipes. This affects other tinkering recipes in more minor ways : you can't remove curses from carved pumpkins and compasses one stack at a time anymore, and if you had a modded item that supported enchantments or trims that was also stackable for some reason, those should be fixed too
-
Fixed the description of the book unsigning feature in the config menu being inaccurate
- It previously said you only needed an ink sac to unsign a written book, when in reality you need an ink sac and a feather
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:HfWBgYPI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LZIfwEFj:HfWBgYPI"
}

