All versions
1.0
Release
Create: Canisters 1.03 days ago 12
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.0
New
- Canisters explode. A dropped canister holding any fluid except lava explodes when destroyed by fire, lava, campfires, cactus or explosions. The fuller it is, the bigger the blast: a full canister is as strong as TNT. Explosions leave patches of fire.
- Flaming arrows detonate placed canisters.
- Chain reactions. Explosions instantly set off nearby canisters, both dropped and placed.
- Place filled canisters with Shift + right click (optional). The fluid stays inside and drops with the block.
- Pipe connection (optional). Placed canisters work as small tanks for pipes, pumps and spouts.
- New config options:
explosionPower,explosionBreaksBlocks,explosionCausesFire,placeFilledCanisters,placedCanistersConnectPipes.
Fixes
- Canister blocks now break when the block below them is removed.
- Leftovers under 1 bucket can now be poured into tanks, and no fluid is lost when a tank accepts only part of a bucket.
- Fuel canisters no longer come back when used as a crafting ingredient (crafting table, crafter, Mechanical Crafter, basin).
- The config is now synced from the server, so tooltips, fill bars and filters show the server's capacity.
- Better performance when rendering the fill bar color.
Notes
- The config is now a server config:
serverconfig/createcanisters-server.tomlin the world folder. Put it indefaultconfigs/for modpacks. The old common config is no longer read. - Requires Create 6.0.10+ and NeoForge 21.1+ for Minecraft 1.21.1.
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:VtRM2vqB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qTgeuk4B:VtRM2vqB"
}

