Tags
Creators
Details
6.0.1
Compatibility
Changes
This is a beta release, currently exclusively for NeoForge 1.21.1 - please report any issues on the GitHub issue tracker
The previously released and removed 6.0.0 version contained game breaking issues, these have been resolved.
XP levels now subtract correctly [#74] Costs containing air (i.e transmute) did not validate correctly [#76] Datapacks did not sync properly between client and server, fixed in latest AlfinoLib version 1.2.0 [#81] Fixed Mixin conflict with MoreJS [#73] 6.0.0 Changelog:
• Requires AlfinoLib 1.2.0
• Added mod filters – press ‘Tab’ when an item is inserted in the enchanting table to show enchantments for specific mods
• Thanks to armandoxtraceroespalda-dev: Items now stay in the enchanting table. The tool is rendered above the enchanting table. Particles now correctly display when filled chiselled bookshelves are nearby.
• Datapack refactored – final revision (see Wiki)
• Added support for data components in cost datapacks.
• Added node API for addon mods
• All enchantments now show up by default in the enchanting table
• All enchantments must now have a valid cost file
• Added clearer error messaging when datapack files are invalid or missing
• Removed ‘Allow Transmute’ and ‘Allow Replicate’ from config – replaced with ‘enable’ and ‘disable’ in their cost files.
• Added config option for enabling/disabling enchanted book villager trades – trade override moved to Mixin instead of event/datapack manipulation.
• Added config option for changing enchanted book loot mode to replace with ancient books or remove.
• Books/Enchanted books now work in the enchanting table.
• Fixed crashes related to invalid datapacks, now displays error messages rather than crashing
• Transmute node now correctly shows as locked if matching enchantment not available
• Fixed hover ordering when there are many nodes that overlap
• Creative bookshelf can now be inserted to see all enchantments
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:DfWQAvS4:1axWAPS7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DfWQAvS4:1axWAPS7"
}

