Tags
Creators
Details
3.0
Compatibility
Changes
Most things in life aren't black-and-white, sometimes you need a shade of gray in between. Now instead of entirely disabling mob-spawns, you can adjust the rates in certain areas. The "factor" parameter of DMZs will alter the vanilla spawn rates, with "0" being fully disabled and "1" being fully vanilla.
I've also cleaned up the config a bunch. This was one of (if not the first?) plugin I made, and the config file was a disaster--requiring every mob being present in the config.
This version does have a slightly new config format. Take note of your existing DMZs and then re-gen the config by deleting config.yml. One day I'll make updates more graceful, but today is not that day.
Paired with this is a significant cleanup of the code that should make this plugin even more lightweight than it was prior.
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:6tHNJbdE:S2GTax0I"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6tHNJbdE:S2GTax0I"
}

