3.0.3-beta
Compatibility
Changes
Here's a hotfix for the latest beta version:
- Now the versions for modloaders work correctly on NeoForge and Forge
- Fixed an issue where trimmed tools had z-fighting in 1.21.1
- Unfortunately, this makes Tool Trims for 1.21.1 imcompatible with resource packs that change tool's textures
- There are no longer errors in the Minecraft log when loading the versions for 1.21.1
There's still a known issue on 26.1.x with NeoForge, making all trims appear white (#3). If you find any other issues, you can now report them in this Github repository.
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:uXeEiQk1:twlf4dnw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uXeEiQk1:twlf4dnw"
}

