Tags
Creators
Details
2.6.0
Compatibility
Changes
Features
- Siege nights: block breaking, block placing, and towering each have a new
eventsoption (/za breaking events on, orzombieBlockBreakingDuringEventsand its placing and towering versions). When it is on, zombies can use that ability during hordes and blood moons before its start day, then all the time once the start day is reached. With a start day of 50, zombies only break and build on event nights until day 50. - Stepped difficulty:
/za scaling steps <days>(scalingStepDays) makes zombie strength rise in jumps instead of a little every day. With10, it rises on days 11, 21, 31, and so on, the morning after each 10-day horde. - Bigger waves over time:
/za scaling extrazombies <count>(maxExtraZombiesPerWave) adds up to that many zombies to every custom wave at full strength, including horde and blood moon waves. It grows with the scaling strength. - The breaking, placing, and towering dashboards now show whether the feature is active right now and whether it also runs during events. The scaling dashboard shows when strength rises next and the current extra wave size.
All new settings default to off, so existing worlds play the same until you change them.
Siege night setup
A horde at nightfall every 10th day, breaking and building only on those nights until day 50, and stronger, bigger waves after each one:
/za events on
/za events interval 10
/za events chance 1
/za events dusk on
/za events duration 10
/za scaling steps 10
/za scaling extrazombies 4
/za breaking on
/za breaking startday 50
/za breaking events on
/za placing on
/za placing startday 50
/za placing events on
Blood moons count as event nights too; use /za bloodmoon off if only the scheduled sieges should allow breaking and building.
Files
zombieapocalypseaddon-2.6.0.jar- NeoForge 1.21.1 (NeoForge 21.1.218+, Java 21)zombieapocalypseaddon-neoforge-1.20.1-1.9.0.jar- NeoForge 1.20.1 (Java 17)zombieapocalypseaddon-forge-1.20.1-1.9.0.jar- Forge 1.20.1 (Forge 47.4.18+, Java 17)
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:gH2XNhDh:MOvAgABb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gH2XNhDh:MOvAgABb"
}

