All versions
1.3.3-1.21.1
Release
ZombiesEverywhere 1.3.3-1.21.13 days ago 59
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Changes
Fixes:
- Fixed the bug where the zombie attack target list configuration could not include mobs from other mods (non-vanilla mobs).
- Reduced the default maximum number of Corruption Gates near players; added randomness to Corruption Gate zombie spawn intervals; increased the default maximum spawn counts for each gate size — more fun and more pressure.
- Significantly reduced the base health and attack damage of normal zombies. Slightly reduced the base attack damage of special zombies.
- Fixed JEI incorrectly displaying enhancement recipes as shapeless recipes. You can now view enhancement recipes for corrupted equipment through JEI.
- Reworked the Piercing Arrow trail effect: no longer uses white particle effects; now uses a custom-rendered light trail that is more performance-friendly and less bug-prone.
New Features:
- Added hot-reload for external config files: you can now edit config files (loot tables, the mob whitelist for zombie-only mode, zombie targets, etc.) and reload them in-game with the command
/zombieseverywhere reload [file]without restarting the game. (Note: the JSON format must be valid — an invalid format will be reset to the default config.) - Besides attacking configured targets, zombies now also attack passively: mobs that damage a zombie will temporarily attract its aggro.
- Players now receive a powerful starter weapon when first entering the world.
- Zombies can now double-jump, allowing them to climb over higher obstacles.
Optional dependencies
Any compatible version
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:SdNhvODs:nBBBZObB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SdNhvODs:nBBBZObB"
}

