1.8.24
Compatibility
Changes
Lots of minor changes, and some major ones as well. Some of these changes are listed below:
Corrupted zones (after becoming deactivated when a player moves too far away) can now become re-activated if a player comes nearby. Corruption points spawn naturally now. Corruption points now spread towards a player more often. Less CPU usage due to corruption point exclusion. Blocks placed by a player are now immune to corruption (as are certain important blocks such as end portal frames). Added block validation in many areas to ensure sanity. And more!™
Blocks placed by a player being immune to corruption is achieved by spawning a third (new) kind of invisible entity. The entity lasts for 51 seconds (1024 ticks).
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:NlNtI94X:bdNVaYH5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NlNtI94X:bdNVaYH5"
}

