1.2.0
Compatibility
Changes
Bug no more.
Fixes variation scaling not working and tweaked it so much that It's practically perfect. Not really needed to lower the mobscaleswithfactor when you add many new advancements since now major story advancements are the things that increase difficulty the most. So getting 100 advancements in a random mod won't make the game unfair anymore. And instead going to the nether or the end or beating the dragon will make the game slightly harder FOREVER!!
Also added a command for my debugging but you can check it out, called "resetvariationscaling"
That's it, I put alot of effort here to fix this bug since it was an annoying one. But yeah, Have Fun!
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:2x5poRUo:Zw3Fm0u8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2x5poRUo:Zw3Fm0u8"
}

