Tags
Creators
Details
1.2.0+neoforge-26.2
Compatibility
Changes
I recommend always making backup of your world before updating anything.
Disclaimer: I cant possibly test all the modloaders with all the Minecraft versions so most of them are copy pasted code from the newest version, fixed to compile and not tested in game. If you encounter bugs please report them on discord below thanks.
Please report issues to my discord https://discord.gg/y366spsSjv
1.2.0
- unified features across versions and modloaders
- backported Riptide_durability_damage config option to the 1.20.1 and 1.21.1
- added commands for changing the mod config values
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:LBIdiCra:jldi0dMA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LBIdiCra:jldi0dMA"
}

