All versions
4.0
Beta
The DB 4.0 | Descent Into Oblivionlast year 235
Compatibility
Minecraft: Java Edition
1.16.4β1.16.5
Platform
Forge
Supported environments
Client and server
Changes
4.0 | Descent Into Oblivion
Added
- π Day 15 Event Remade β the fifteenth-day event has been completely redone.
- π More Than Half of Existing Events Updated β many day events have been improved and expanded.
- π§© 15+ New Events Added β over fifteen new events have been introduced.
- π¨ Visual Updates β various visual improvements and adjustments were made.
- π¬ Chat Interactions Added β new player-chat interactions are now part of the experience.
- πͺ Minecraft UI Updates β several in-game visuals have been updated.
- π± Nightmare Events Added β new terrifying nightmare sequences were introduced.
- ποΈ New Structures Added β new naturally generated structures can now appear in the world.
- ποΈ New Entity Added β a new entity has been introduced.
- π Lore Expanded β the story and background have been further developed.
- π Ending Completely Rewritten β the modβs ending has been fully changed and recoded.
- βοΈ DB Despawn Behavior Slightly Modified β small changes were made to DBβs despawn mechanics.
- π§± New Structure Formation Added (Extremely Rare) β a new, very rare structure can now generate.
- π©Έ Existing DB Variant Made More Terrifying β one DB variant (no spoilers) has become much scarier.
- π New DB Variant Added β an entirely new DB variant has been added.
Fixed
- π Multiplayer Issues β some small multiplayer bugs and desync issues have been resolved.
- π Many Bug Fixes β numerous existing issues resolved.
- π Added Forge 36.2.34 and 1.16.4 support(really)
Normally, this version of the mod would have been released on October 31, but it couldn't be released due to Microsoft's crash.
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:Suj0CNYJ:HrE8NrvD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Suj0CNYJ:HrE8NrvD"
}

