Tags
Creators
Details
1.20.1-3.1.0
Compatibility
Changes
The huge improvements to Dramatic Doors is now on 3.1.0. You no longer need Sinytra Connector but it remains compatible for cross mod-loader compatibility! Dramatic Doors can simultaneously support both Forge and Fabric mods in one running instance!
- (3.1.0_1) Fixed potential crash with Supplementaries.
- Completely restructured the code into Common, Forge, and Fabric.
- Common is where assets reside and blocks, items, block entities, and the registries are declared.
- Forge and Fabric code handle their methods of registration.
- Added support for the following mods:
- Alex's Caves.
- The Aether: Redux
- Desolation
- Enderscape
- Added tags for Aether Redux, Atum, Aurora's Decorations, Better Archaeology, Blockus, Enderscape, Modern Glass Doors, and Traverse.
- Removed Twigs support due to Twigs having removed Stripped Bamboo doors.
- Re-added Blocks+ support, it was mistakenly omitted. Oops!
- Changed Blockus bamboo doors to tall and short version of Raw Bamboo doors.
- All forms of short and tall Netherite doors can no longer burn in lava.
- Coded support for Aurora's Decorations, currently awaiting permission for door textures.
- Updated various tall door textures for Abnormals mod compat. Affected doors: Atmospheric, Autumnity, Buzzier Bees, and Upgrade Aquatic.
- Updated short Honeycomb door item texture to match the updated Honeycomb door item textures.
- Fixed Horizons Cypress doors texture.
- Fixed recipe for Short Echo Doors.
- Soulcopper doors are now pickaxe-mineable.
Optional dependencies
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| DramaticDoors-QuiFabrge-1.20.1-3.1.0_1.jar | Unknown | 9.58 MiB |
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:DaktlCLV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aQ7h7gal:DaktlCLV"
}

