
Create: Completely Create
A lightweight Create addon that adds dozens of new, balanced, automation-friendly recipes for blocks, items, and materials. From improved stone processing and decorative block conversions to advanced mixing, crushing, and compacting chains.(ALSO HAS TUFF)
Tags
Creators
Details
2.2.1
Compatibility
Required content
Changes
Bug Fixes
- Fixed brass expellers never producing output while the output slot is empty: NeoForge's
ItemStack.EMPTY.getMaxStackSize()returns 1 (no MAX_STACK_SIZE component), so every multiplied insertion was rejected as exceeding the stack limit; capacity checks now measure against the recipe result stack - Output-space validation now accounts for the full multiplied output even when the output slot is empty
- Fixed extruders accepting flowing liquids as water/lava/ice equivalents; only source blocks count now (applies to side ingredients, catalysts, and blocks consumed by advanced recipes)
- Fixed paxels draining a full backtank of air (900) per durability point instead of 1; air cost is now scaled against the tool's max durability, matching createqol's basic tools
- Fixed extruding block tags failing to load when Create: Connected or Create: Aeronautics are not installed — cross-mod entries are now optional (
"required": false), unblocking all extruding recipes - Fixed brass
outputMultiplierbeing defined at a doubled config path (block_expeller.brass.outputMultiplier.outputMultiplier); it now lives atblock_expeller.brass.outputMultiplier - The Config button on the Mods list screen is now clickable and opens NeoForge's built-in config screen
Changes
- Extruder output inventory is now accessible from all sides (was extraction-from-below only)
- Brass extruder default cycle time reverted to 240 ticks
- Added COMMON config type registration (
createcompletelycreate-common.toml, currently empty)
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:D0su1oRx:KBwMgHwo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:D0su1oRx:KBwMgHwo"
}
