Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published last year
All versions
1.11.0
Beta
Create: Dragons Plus 1.11.0 for Create 1.21.1-6.0.10last month 1,435
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
Create: Dragons Plus 1.11.0
Added
- Add Dye Fluid and Bulk Coloring support for Dye Depot, Dyenamics and Arts & Crafts (Bleachdew as a special "dye"). Dye Fluid bucket variants, recipes, tags, JEI entries, lava interactions and break effects for Fragile Fluid Tanks for supported extra dye colors.
- Add The Aether support: Bulk Freezing can now process Aether Freezer recipes. Add Bulk Enchanting for The Aether Altar recipes using Golden Aercloud as the fan catalyst. Bulk Enchanting can incubate Aether Moa Eggs into Moas.
- Player can search recipes in JEI via dye fluid and dye fluid bucket.
- Liquid Dragon's Breath can now slowly fill cauldrons through pointed dripstone. Dragon's Breath Cauldrons hold four bottle-sized levels and can be filled or emptied with Dragon's Breath bottles and buckets.
Changed
- Bulk Coloring now supports namespaced dye variants instead of only vanilla dye colors
Fix
- Bring back Bulgarian Localization (by @Boris Valkov)
- Fix Automated Brewing with Liquid Dragon's Breath doesn't respect priority
- Fix Major TPS Lag: ColoringFanProcessingType performs expensive recipe lookups on every Chute/BlockEntity tick
- Fix fluid hatch algorithm prevents fluid from being operated in certain cases. (such as conflict with create stuff additions tank)
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| CreateDragonsPlus-1.11.0-sources.jar | Unknown | 652 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:EAW88SvH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dzb1a5WV:EAW88SvH"
}


