All versions
v3+mod
Release
DnT Nether Fortress Overhaul v3last year 67.3K
Compatibility
Minecraft: Java Edition
1.21.5ā1.21.8
Platform
Fabric
Supported environments
Changes
Dungeons and Taverns Nether Fortress Overhaul v3
- Overhauled the Nether Fortress from the ground up
- none of the v2.7 parts are used because of that
- meaning this will no longer cause issues with the Nether Keep from Dungeons and Taverns
- The Lava well hours has been fully overhauled but still has a guaranteed blaze spawner but also 3 additional vanilla fortress chests
- The Bridge has been fully overhauled to be much more brutalist, slim bust still keeps its inside part
- Every bridge piece has a 1/4 chance to spawn a chest with the vanilla fortress loot
- Every Bridge Intersection part (that's the part between 2 crossroads as example, they are always straight) has a 1/6 chance to spawn a Blaze Spawner Tower (if there is space for it)
- The entire Fortress Inside halls part has been overhauled
- There are 3 types of hallway parts:
- Slim: those hallway parts have a chance to spawn a vanilla fortress chest or decoration or just nothing at all.
- Stairs: meaing the stairs part, this one always goes 1 level down. Netherwart stairs and Blaze Stairs, those split the nether fortress hall part to continue on the same level and 2 levels higher
- Wings: meaning those parts can contain rooms, there are 30 7x4x7 rooms and 11 7x4x15 rooms (includes rooms with blaze spawner and magma cube spawner)
- Rooms can have chests with the Overhauled Nether Fortress Loot chest. those roll once for the vanilla nether fortress loot to ensure mod compability and then for a custom loot table made for this overhaul
- Curves cant connect to other curves
- Wings cant connect to other wings
- There are 3 types of hallway parts:
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:8Dbnvm77:LdhYCmj8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8Dbnvm77:LdhYCmj8"
}

