Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated last month
All versions
26.201.2
Beta
better-nether-26.201.2last month 48.6K
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client and server
Required content
Changes
Changes
- Molten gloomsculk emits light 2 rather than 5
- Molten gloomsculk is cut from the bleached crust, not from sculk
- Pale gloomgrass no longer fades to near-black at its base
- The gloomwood floor is now four fifths bleached gloomsculk
Fixes
- Fortresses and terrain features overwrote nether cities
- Spawners in already-generated worlds kept their unreadable gear
- City guards spawned without their gear
- Nether mob spawners never spawned anything (MC-30744)
- Stalagnate wart bowl rendered as a missing-texture full block
- Flaming ruby tools rendered flat instead of handheld (BetterNether#310)
- Nether saplings never grew on their own, and were planks
- Gloomwisps paid experience into the player, and only ever a player
- Saplings could not be composted by a hopper
Validation
- ✅ BiomesOPlenty + Terralith (BiomesOPlenty-fabric-26.2-26.2.0.0.27.jar, Terralith_26.2_v2.6.4.jar, GlitchCore-fabric-26.2-26.2.0.0.0.jar, TerraBlender-fabric-26.2-26.2.0.0.2.jar, lithostitched-1.7.13-fabric-26.2.jar, tested: gametest+worldgen)
- ✅ Incendium alone (Incendium_Legacy_26.2_v5.5.0.jar, tested: gametest+worldgen)
- ✅ Nullscape alone (Nullscape_26.2_v1.2.20.jar, tested: gametest+worldgen)
- ✅ BOP + Terralith + Incendium + Nullscape (BiomesOPlenty-fabric-26.2-26.2.0.0.27.jar, Terralith_26.2_v2.6.4.jar, GlitchCore-fabric-26.2-26.2.0.0.0.jar, TerraBlender-fabric-26.2-26.2.0.0.2.jar, lithostitched-1.7.13-fabric-26.2.jar, Incendium_Legacy_26.2_v5.5.0.jar, Nullscape_26.2_v1.2.20.jar, tested: gametest+worldgen)
Optional dependencies
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:MpzVLzy5:iBR9QMPF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MpzVLzy5:iBR9QMPF"
}






