All versions
1.0.2-neoforge+mc26.1.2-beta
Beta
ZombiesEverywhere 1.0.2-neoforge+mc26.1.2-beta3 days ago 22
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
V1.0.2 Changelog
Fixes
- Loot system rework:
In the old loot system, players could not change a zombie's drop rules on their own through config files, and the files were misleading.
This update reworks the loot system:
- The drop types no longer differ by zombie-only mode. The only difference is that with zombie-only mode off, the default zombie drop chance is just 50% of the configured value.
- Zombie loot comes from two config files:
common.jsonand<zombieName>.json. common.jsonholds the drops shared by every zombie type - configure it there, for example, to make all zombies drop a Nether Star.<zombieName>.jsonholds one zombie's own drops - to make only Elite Zombies drop a Dragon Egg, configure it inelite_zombies.json.- Say you want Elite Zombies to drop Rotten Flesh more often, but that entry lives in
common.json, and editing it there would affect every other zombie too. No need to worry: write the same-named Rotten Flesh entry inelite_zombies.jsonand it overrides the common one. - New command:
/ze loot preview <type>prints the expected drops per dimension for each zombie type, to help tune the numbers. - Assigning third-party mod items to zombies is supported as well.
Additions
- Fully ported and synced from the 1.21.1 mainline V1.4.3, plus selected features from V1.4.4.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
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:I2jENCur"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SdNhvODs:I2jENCur"
}

