All versions
1.0.3-hotfix2
Release
OneEnoughDamage-neoforge-1.21.1 1.0.3-hotfix2last month 13
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Changes
1.0.3-hotfix2
- Fixes the Forge 1.20.1 build: 1.0.3-hotfix1 shipped a development (named-mapping) jar whose attribute registration crashed the game at startup with NoSuchMethodError: RangedAttribute.setSyncable(boolean).
- The publish task now always uploads the reobfuscated production jar, so build/devlibs can no longer be picked up.
- Fabric and NeoForge are republished unchanged apart from the version number, keeping every loader on the same release.
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:Do4L2Cgy:mLCm3Xcu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Do4L2Cgy:mLCm3Xcu"
}

