Tags
Creators
Details
1.3.8
Compatibility
Changes
Fixed a second NeoForge module-resolution crash: a leftover NeoForge internal service registration (net.neoforged.fml.IBindingsProvider) was leaking into the shaded jar and causing protectcord to falsely claim ownership of NeoForge's own internal package, colliding with the real neoforge module. Also fixed the bundled MySQL JDBC driver registration, which was broken by the earlier relocation fix (wrong/stale class name meant MySQL storage silently failed to initialize on every platform). Development/test build for verification before promotion to a stable release.
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:y05wfnBZ:HWNeNPgx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:y05wfnBZ:HWNeNPgx"
}

