Tags
Creators
Details
1.2.2
Compatibility
Required content
Changes
Changelog
1.2.2
Fixed
-
NeoForge builds no longer crash when you join a world on Minecraft 1.21 through 1.21.6. NeoForge moved the client-side packet send into a new class in 1.21.7 and removed the old one. This build covers 1.21 through 1.21.8, both sides of that move, and was compiled against the newer Minecraft — so on 1.21.6 and earlier the class it reached for was not there and the game came down the moment the mod greeted the server.
The right class is now looked up when the mod loads, so one build works across the whole range.
Only NeoForge was affected. Fabric never had this, and nothing else changed.
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:LLsfORx9:dAa6npEA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LLsfORx9:dAa6npEA"
}

