Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated 9 months ago
All versions
1.18.2-2.1.5
Release
DD 1.18.2-2.1.5 (Forge)4 years ago 92
Compatibility
Minecraft: Java Edition
1.18.2
Platform
Forge
Supported environments
Client and server
Changes
From 2.1.5:
- Added support for the following mods:
- Biomancy
- Blue Skies
- Caupona
- Hexerei
- Malum
- IntegratedDynamics
- Tinkers Construct
- Now requires Forge 40.1.80+ for the sake of staying up to date.
- Updated the credits a bit.
- Updated textures of Tall Redbud Doors.
- At last, waterlogged fence gates now work with Supplementaries!
- Waterlogging for doors and fence gates are now on by default when the mod is initialized for the first time.
- Adjusted client rendering for BYG doors. Most of them will use Cutout, except for a few doors with translucent windows.
- Overhauled Mixin to ensure that custom mobs that can open doors also can open tall doors.
From 2.1.4:
- Added support for the following mods:
- One Twenty Backport
- Chipped
- Forbidden & Arcanus
- New World
- Removed Bamboo Blocks support as that mod is effectively abandoned. One Twenty Backport is the replacement.
- As such, the tall bamboo door textures have been changed to be based on vanilla 1.20 bamboo doors.
- Added support for swamp doors from Macaw's Doors 1.0.7+.
- Updated Tall Oak Door texture to add the missing middle hinge.
- Internal additions: Added data generation to allow for ease of generating massive amounts of tall door block states and models.
- Internal changes: Fallback door blocks can be chosen as opposed to always oak door, to allow for more consistent behaviour.
- Added item category tags for modded doors for use with KubeJS.
- Some tag tweaks.
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:aQ7h7gal:yGjnVOZh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aQ7h7gal:yGjnVOZh"
}

