1.0.1+1.20.1-forge
Compatibility
Required content
Changes
1.0.1
Fix: 1.20.1 Forge mixin crash on load
Players on Minecraft 1.20.1 Forge hit:
MixinTransformerError / MixinApplyError: OtterEntityMixin … FAILED during APPLY
Cause: the pearl-boost inject targeted mojmap eat with remap=true, but the published jar has an empty refmap, and Critters and Companions ships the method as SRG m_5584_.
Fix: inject into m_5584_(Level, ItemStack) with remap=false (same approach as 1.18.2 / 1.19.2 Forge and 1.20.1 NeoForge).
Fabric and NeoForge 1.20.1 were already correct; only the Forge 1.20.1 jar needed this change.
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:hDnX08L0:7AUod42f"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hDnX08L0:7AUod42f"
}


