Tags
Creators
Details
Licensed ARR
Published 3 years ago
Updated yesterday
All versions
2.8.0
Release
Zombie Apocalypse Addon 2.8.0 - NeoForge 1.21.1yesterday 256
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Server-side
Client and server
Changes
Changes
- Better fresh-install defaults. The first day (day 0) is now safe in daylight so players can gather gear; nights are not. Scheduled hordes now arrive at dusk and last about the whole night (10 minutes) instead of starting at dawn for 5 minutes. Existing configs keep their values; run
/za preset standardto switch to the new balance. - Presets now set hordes to arrive at dusk, and their horde lengths cover the night: Casual 6 minutes, Standard 10, Hardcore 12. Casual now protects every lit area like Standard does.
/za dayshows the time as a clock with the phase, for example19:30 (night), and warns that vanilla/time setresets the day counter.
Fixes
- Forge and NeoForge 1.20.1: an in-game change made while the config file was missing lines no longer writes defaults for those lines, and a hand edit picked up by an in-game change is now announced to operators like other file edits.
- The
[compatibility]section comment pointed at/za compatibility onfor restoring safeguards; it now points at/za config reset compatibility.
Documentation
- New wiki pages: a Config Reference with every setting, its default, allowed range, and description, generated from the mod, and an FAQ.
- The README, descriptions, and wiki now list exactly what a fresh install does and compare the three presets value by value.
Files
zombieapocalypseaddon-2.8.0.jar- NeoForge 1.21.1 (NeoForge 21.1.218+, Java 21)zombieapocalypseaddon-neoforge-1.20.1-1.11.0.jar- NeoForge 1.20.1 (Java 17)zombieapocalypseaddon-forge-1.20.1-1.11.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:VJNY5aOr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gH2XNhDh:VJNY5aOr"
}

