3.2.0_lts
Compatibility
Changes
I will be doing a new thing here (for as long as I can), and still be releasing new versions for both Minecraft 1.17.1 as well as slightly older 1.16.5, due to there not being very many mods/packs from old times being updated just quite yet, apart from yours truly and a few others. I can so why not.
-These releases will not only be releases straight from the get-go, but they should also be way more stable than the 1.17.1 versions of the mod, although are built from the exact same place, and from the same original hosted source.
Including...
-This release is version 4.0.1 of the 1.17.1 line, but for 1.16.5, hence why it's also version 3.2.0. version 1 was for 1.15.2, version 2 was for 1.16.4, version 3 was for 1.16.5 and still is, and version 4 is for 1.17.1.
Thank you.
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:nVWmFwF8:WTS2Jdwh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nVWmFwF8:WTS2Jdwh"
}

