Links
Tags
Creators
Details
1.0.4+mcb1.7.3
Compatibility
Changes
Ornithe libraries (OSL and friends) ship .classtweaker files, the accesswidener successor. They carry the same intermediary token soup, so both the converter's text-resource rewrite and the plugin's residue scan now handle them like accesswideners.
Those same libraries are multi-version and compiled against the newest version in their range, so they reference members that do not exist in b1.7.3. Calamus numbers every version separately, so there is nothing to convert those tokens to. The post-conversion residue check now splits leftovers into tokens the b1.7.3 map actually covers (real gaps, still a warning) and the rest (logged at info instead of shouting about a gap that cannot exist).
Also drops the b1.7.3 method entries that never existed there.
Mod and gradle plugin both at 1.0.4.
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:mKBqWXD0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8bXIXbjV:mKBqWXD0"
}

