1.1.1+neoforge
Compatibility
Changes
Fixes
- Corrected pack compatibility metadata for Minecraft 1.21.1–1.21.8.
- Added support for the older enchantment-component layout without processing a crop twice.
- Improved installation diagnostics and safe availability-tag references.
- Included installation instructions in the download.
Installation / updating
Use the Neoforge JAR in the instance's mods/ folder, replace the previous copy, and restart Minecraft or the server. /reload alone does not register newly installed custom enchantments.
For multiplayer, install on the server. A client-only installation cannot enable the pack on a remote server. Keep only one installed copy of this pack (ZIP or JAR).
Hold an enchanted hoe and keep matching seeds in your inventory. Replanting requires suitable ground.
Compatibility
Compatibility fixes validated on the listed Java Edition releases, including Minecraft 26.2.
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:jt3edG9b:9Tp2YwWR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jt3edG9b:9Tp2YwWR"
}

