Tags
Creators
Details
Licensed ARR
Published last year
Updated 2 months ago
All versions
1.1.2
Release
ZombieApocalypse999 1.1.2last year 89
Uploaded by
Compatibility
Minecraft: Java Edition
1.21โ1.21.9
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
New Mutations
- Added Cryo Zombie: A frost-based zombie with abilities focused on slowing and freezing players.
- Added Inferno Zombie: A fire-based zombie that creates environmental hazards and attacks from a distance.
Configuration Rework
- Modular Mutations: The
config.ymlfile has been restructured to make all mutations modular. Each mutation type now has its own subsection for easier management. - Customizable Abilities: All abilities for the new Cryo and Inferno zombies (e.g., freeze chance, fireball cooldown) are now fully customizable in the config.
- Simplified Disabling: Mutations can now be disabled by setting their
spawn_chanceto0. The separateenabledflag has been removed. - Configuration Warning: The server console will now display a warning message on startup for each mutation that has a spawn chance of 0, to alert server owners of intentionally or accidentally disabled mutations.
Command Updates
- The
/za spawncommand has been updated to allow for manual spawning ofcryoandinfernozombies. - The help message for the command now lists the new zombie types.
Zombie Population Control
- Worldwide Zombie Limit: Added a configurable
max_worldwideoption (default: 100) to limit the total number of special zombies allowed to exist in the world at one time. - Per-Chunk Zombie Limit: Added a configurable
max_per_chunkoption (default: 20) to prevent too many zombies from spawning in a single chunk. - Dynamic Spawning: The zombie spawning system now respects both the worldwide and per-chunk limits, preventing new spawns if either cap is reached.
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:slkp22JH:Dsdxj8J0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:slkp22JH:Dsdxj8J0"
}

