Links
Tags
Creators
Details
1.0.1
Compatibility
Required content
Changes
Patch Notes - Shulker Vault v1.0.1
Feature added
Advanced shulker vault now wakes Frogports to properly deploy packages when given a redstone signal.
added wakeTheFrogs() for item handling.
Patch Notes - Shulker Vault v1.0.0
New Blocks
Shulker Vault
A 27-slot storage block with 4x stack capacity (256 items per slot) Animated lid that opens and spins like a vanilla shulker box Players standing on top are lifted smoothly as the lid opens Works with hoppers, funnels, chutes, and Create automation Can be picked up with a Create wrench, preserving all contents Displays the item in the currently hovered slot while the GUI is open
Advanced Shulker Vault
Upgraded version with all base vault features plus Create package support Crafted via Mechanical Crafting: Electron Tube + Packager + Shulker Vault Preserves inventory contents during upgrade Package Receiving: Automatically unpacks incoming packages into storage Package Slot: Dedicated overflow slot holds packages that can't be unpacked Redstone Packaging: Pulse with redstone to create a package from vault contents Sign Addressing: Place a sign adjacent to set the package destination address Greedy extraction fills packages from one slot before moving to the next
Features
Oversized Stacks: Hold Ctrl+Shift and click to transfer entire oversized stacks All-or-Nothing Unpacking: Packages only unpack if ALL contents fit (no partial scatter) Automation Friendly: Full IItemHandler capability support for Create and vanilla systems Inventory Safety: Vaults cannot be placed inside shulker boxes, bundles, or other vaults Technical NeoForge 1.21.1 Requires Create 6.0+ Stack multiplier configurable (default: 4x) Notes Shulker Boxes, backpacks, bundles, and other shulker vaults are unable to be stored in this inventory for memory safety.
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:T9EwlKPc:8Eme5gHs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:T9EwlKPc:8Eme5gHs"
}

