1.6.0
Compatibility
Changes
Enchanters
The enchanting table itself is now data-driven! Any block can become an enchanter with its own effects, catalyst limit, and range!
Scrolls
Scrolls can now add multiple levels of an enchantment! This means scrolls can no longer use a list or tag, so it does result in breaking changes!
Misc.
- Renamed
enchanting_statustoused_levelsandinnate_enchantmentstosealed_enchantments. Previous versions would still migrate automatically. - Removed unused gamerules
- Moved normalized enchantments into a built-in datapack.
- Enchanting now gives the Enchanter advancement
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:HiPMHSof:86AeTtoP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HiPMHSof:86AeTtoP"
}

