All versions
1.2.0
Release
ZEN's Upgraded Netheritelast week 19
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Changes
1.2.0
🔧 Fixes and Optimizations
Fixes
- Improved automatic tree cutting with the Singularite Axe.
- Jungle trees, separated logs, and distant branches are now detected correctly.
- Increased the maximum number of logs Tree Cutting can process.
- The Singularite Hammer now ignores unbreakable blocks during 3×3 mining.
- The Singularite Hammer now only accepts compatible mining enchantments, including enchantments added by other mods.
- Fixed the Tier V Vitality Rune exhaustion effect.
- The crop growth effect now covers the player's chunk and the eight surrounding chunks.
- End City treasure chests now have a 5% chance of containing a rune.
- Applying a rune now always costs 30 experience levels, regardless of its tier.
- Mobs spawned with modded equipment through commands, datapacks, or other mods no longer lose their equipment.
- Improved ore detection for the automatic smelting ability.
- Vanilla Emerald Ore generation is no longer removed, improving compatibility with datapacks and other mods.
- The mod's custom deep Emerald Ore generation remains available.
- Improved the Void Totem's safe-position search.
Optimizations
- Optimized JEI rune recipes while keeping every armor and rune combination available.
- Improved Tree Cutting detection and processing.
- Improved compatibility with modded enchantments and ores.
- Reduced unnecessary calculations related to crop growth effects.
- Improved overall stability in single-player and multiplayer.
Configuration
- Added a server configuration file with options for the mod's main features.
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:EpxawZNl:fFedSi6b"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EpxawZNl:fFedSi6b"
}

