2.6
Compatibility
Required content
Changes
🛠️ Version 2.6: The NeoForge Update
Target Version: Minecraft 1.21.11 Loader: NeoForge (1.21.11+)
This update marks a significant milestone as I have officially transitioned the mod to the NeoForge ecosystem. This move ensures better compatibility with the modern modding landscape and improved performance.
Optional dependencies
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:URQ0rty4:IstJTCUu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:URQ0rty4:IstJTCUu"
}

