Tags
Creators
Details
Licensed ARR
Published 4 months ago
Updated 23 hours ago
All versions
1.3
Release
Create: Canisters 1.323 hours ago 100
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1–1.21.11
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Create: Canisters 1.3
New
- Ponder: Making Canisters. Hold W over a canister or any part of the chain (pulp, juice, bioethanol, pellets, sheets) to see the whole production chain in one scene, from sugar cane to a finished canister.
- Fill placed canisters with buckets (optional): right click a placed canister with a filled bucket to pour it in.
- Sable support. Canisters work on Sable ships and other moving structures. They explode and set each other off there, and dropped canisters blow up on campfires that ride on a ship. Sable is optional.
- 14 new languages: German, French, Spanish (Spain and Mexico), Portuguese (Brazil), Italian, Polish, Czech, Ukrainian, Turkish, Japanese, Korean, Chinese (Simplified and Traditional). Create terms match Create's own translations. Corrections are welcome.
Changes
- New main option
placedCanistersHoldFluid. It controls all fluid features of placed canisters: placing filled canisters, pipe connection and bucket filling. Those options now only work while it is on. Engineer's Goggles and comparators also follow it. - Config screen: the placed canister fluid options are shown under the main option and hidden while it is off.
⚠️ Updating
If you used placeFilledCanisters or placedCanistersConnectPipes, turn on placedCanistersHoldFluid after updating, or those options will stop working.
Optional dependencies
Any compatible version
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:qTgeuk4B:3PoCyTYJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qTgeuk4B:3PoCyTYJ"
}

