Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 2 years ago
Updated last month
All versions
1.1.7
Beta
Create: Dragons Plus 1.1.7 for Create Fabric 1.20.1-6.0.8.12 months ago 327
Uploaded by
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Create: Dragons Plus 1.1.7
Fixed
- Fixed consuming open pipe effects calculating their remainder after Create could place the fluid in the world and clear the pipe's internal tank.
- Preserved the exact unconsumed fluid remainder, including NBT data, while keeping transaction rollback and simulation paths side-effect-free.
- Prevented consuming open pipe effects from falling back to Create's fluid-block placement path; non-consuming handlers retain Create's original behavior.
- Fixed the production-only Fabric startup crash reported in #104, caused by Preview 2 mixin targets not surviving namespace remapping.
- Kept the startup fixes from #103 while replacing the affected mixin selectors with production-safe targets.
- Restored Fabric behaviour-provider lookup for block entities that do not extend Create's
SmartBlockEntity. - Preserved water and lava contained by
WaterAndLavaLoggedBlockimplementations when contraptions assemble and disassemble.
Compatibility
- Targets Java 17, Minecraft 1.20.1, Fabric Loader 0.17.2 or newer, Fabric API 0.92.6 or newer, and Create Fabric
>=6.0.8.1 <6.1.0.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| create-dragons-plus-fabric-1.20.1-1.1.7-sources.jar | Unknown | 558.98 KiB |
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:dzb1a5WV:DguHtXXu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dzb1a5WV:DguHtXXu"
}

