Tags
Creators
Details
Published last year
All versions
1.2.4
Release
NetherEx 1.2.4 - NeoForge 1.21.45 months ago 88
Compatibility
Minecraft: Java Edition
1.21.4
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
Version 1.2.4
Added:
- New block and item tags
Fixed:
- Wisp name not being in the translation file
Version 1.2.3
Fixed:
- A crash when using Concurrent Chunk Management Engine (C2ME)
- Netherrack Paths dropping Gloomy Netherrack instead of their respective Netherrack types
Version 1.2.2
Fixed:
- A crash when fertilizing Fungus Blocks.
- A crash when YUNG's Better Nether Fortresses is installed.
Version 1.2.1
Fixed:
- Biomes having incorrect tags
Version 1.2.0
Added:
- Nether Weather support
- Nether Fortress tracking Compass to Bastion Remnant chest loot
Updated:
- Block, Item, and Biome tags
Fixed:
- Player arm not swinging when placing blocks
Other:
- Backported to 1.21.1
Version 1.1.2
Added:
- New Advancements
Updated:
- Mob spawning
- Advancement text and icons
- Gentle and Rough effects to have swapped functionality
Fixed:
- Hoglin loot drops
- Mogus spawns causing reduce Nether spawns
- Flaemoths having step sounds
- Shroomlights not dropping items
- Missing Netherite Nugget recipes
Version 1.1.1
Fixed:
- Resourceful Config missing from mod dependencies
Version 1.1.0
Added:
- Decay functionality to Wither Bonemeal
- Quartz Ore and Gold Ore for the new Netherrack types
- Breeding to Salamander, Mogus, and Flaemoth mobs
- Config using Resourceful Config
- Kiln (A furnace that has twice the speed in the Nether)
- Orange fog color to the Torrid Wasteland
- Advancements
Updated:
- Textures for Warped Fungus and Warped Fungus on a Stick
- Tags for blocks and items
Fixed:
- Block mining issues
- Mogus spawn rate
Version 1.0.0
Initial 1.21.4 release
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:2PIVd4Ik:os02TS3r"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2PIVd4Ik:os02TS3r"
}




