2.0.4
Compatibility
Changes
fixed a stack overflow that would happen if you did too much damage (now unless you somehow deal 1 billion damage in one go it won't happen again)
added a few config elements that haven't been implemented yet
(THIS VERSION HAS MOST LIKELY RESET YOUR CONFIG PLEASE GO CHECK IT BEFORE GOING INTO A WORLD)
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:jqbl72yn:OSVAZ8Ym"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jqbl72yn:OSVAZ8Ym"
}

