Tags
Creators
Details
2026.08.29-neoforge-1.21.1
Compatibility
Changes
ModderNameLib v2026.08.29 for Minecraft 1.21.1
I rewrote the ENTIRE build system; all of my mods are now built with a new build pipeline that's faster and clearer than before. Kinda proud of it but I also want to push out a build to make extra sure nothing has broken in the meantime.
- Compile with new tooling.
- Push down blockentity renderer utils (preparation for 26.1; it finally stopped being crossroadable)
- (All Forge and Neoforge versions) Cut down on startup logspam.
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:zSoTsKbP:WOPUQDoi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zSoTsKbP:WOPUQDoi"
}

