Tags
Creators
Details
0.1.0-1.21.4
Compatibility
Changes
Features
Hoppers Insert into Bundles
A hopper pushing items into a decorated pot that is filled with a bundle will push items into the bundle.
Strict Insert Mode
If the decorated pot being inserted into is made of 3 or more Sherds (not bricks), the hopper will only insert into the bundle items that the bundle already contains. That is, if a bundle has two of each of the wool blocks, any wool block that goes through the hopper will be able to be pushed into the bundle, but no non-wool blocks will be.
Hoppers extract from Bundles
A hopper extracting items from a decorated pot that has a bundle in it will extract items from the bundle first. Items will be extracted, as able, taking one item at a time from the largest stack inside the bundle.
Comparators Read Bundle Fullness
A comparator reading from a decorated pot which contains a bundle will, instead of constantly outputting 15, output a reading based on the bundle's fullness: It will always output a minimum reading of 1.
Dispensers Can Place Decorated Pots.
This might seem like an odd inclusion, but if you wanted to fill a bundle by hopper, while hoppers can extract items from a bundle, the only way to get the bundle out of the pot while still full of items is to break the pot. Meaning that fully automating the bundle filling process requires being able to automatically replace the decorated pot.
Planned Features
Currently there is no visual distinction for a decorated pot with a bundle in it. I'd like to add one for all 17 flavors of bundle. I'm not familiar with the rendering engine enough to make it happen for v0.1.0.
Not Planned Features.
I ain't giving the decorated pots a UI. Dats too much work. If y'all wanna go at it, have fun.
Known incompatibilities
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:IBSY8NfL:WC1rtKvP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IBSY8NfL:WC1rtKvP"
}

