Links
Tags
Creators
Details
1.7.10
Compatibility
Changes
Added: New kill mode, this mode is enabled by default, and will actually kill the mob, and remove them from the world in addition to preventing their spawning, when they try to spawn. When this option is set to false, the removal feature will behave similarly to 1.0.0, where only the spawning of the mob is prevented, and the mob was not actually removed from the world data. This was previously an issue, and would cause all of the prevented mobs to spawn into the world, as soon as the mod was removed, or they were taken off the list of bad mobs. This could lead to potential memory leaks, and has been treated like a bug, however the option to re-enable it is added as this may be beneficial for short term projects.
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:2NEKo1EX:atwtQ416"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2NEKo1EX:atwtQ416"
}

