Links
Tags
Creators
Details
1.0.3+mcb1.7.3
Compatibility
Changes
Fixes two gaps in ornithe -> babric reverse conversion that left calamus tokens in the output jar. Both surfaced at launch as InvalidInjectionException: could not find any targets matching 'm_NNNNNNNN'.
- Falsely ambiguous method tokens. A calamus token declared on several owners but mapping to a single babric token was treated as ambiguous and dropped from the bare-name reverse map, so mixin annotation strings (which carry no owner) were never converted. 6 of the 9 reverse-disambiguation entries in the shipped table were affected.
- Access wideners named
<modid>.accessWidener. Extension matching was case-sensitive, so those files were copied through untouched with their calamus field tokens intact.
babricJar now scans its own output and warns with any calamus tokens it finds, so a mapping gap shows up at build time instead of at mixin apply.
1.0.2 is skipped.
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:8bXIXbjV:cp4zkZdZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8bXIXbjV:cp4zkZdZ"
}

