
Shulker in a Shulker
Store shulker boxes inside other shulker boxes with configurable nesting depth, anti-dupe protection, and admin GUI control. Perfect for survival servers - includes /ns commands, cooldowns, item blacklisting, and full permission customization.
Links
Tags
Creators
Details
1.1.0
Compatibility
Changes
NestedShulkers ā Changelog
v1.1.0
Bug fixes, GUI overhaul, and new Blocked Items manager
š Bug Fixes
- Layer limit ignored ā The max-layers setting was completely ignored at runtime because the code was accidentally reading
max-shulkers-per-shulker(default: 9) instead ofmax-layers. The configured layer limit now works correctly. - Items disappearing after layer 2 ā When closing a nested shulker, contents were only saved into the immediate (innermost) layer and never propagated back up the parent chain. Closing layer 3 would save into layer 3's item, but layer 2 never got updated, so everything above layer 1 appeared empty on re-open. The close handler now walks the full stack from innermost to outermost, updating each parent before writing back to the player's inventory.
⨠New Features
-
Blocked Items GUI ā Accessible from the Settings GUI via the new Blocked Items button (red concrete, centered on row 4). Shows every currently blocked material as its actual in-game item. Players with the
nestedshulkers.blocklist.managepermission can:- Add an item by holding it in their main hand and clicking any empty slot
- Remove an item by clicking it in the GUI
- Changes save to
config.ymlinstantly. The list is paginated (45 items per page) with previous/next navigation.
-
New permissions
nestedshulkers.blocklist.manageā Allows adding/removing items from the blocklist via GUI (default: op)
-
New config messages
blocked-item-added,blocked-item-removed,blocked-item-already,blocklist-no-item
If you want to test if everything is working properly please deop cause op players bypass all permssions.
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:Xhue2TTs:rqcTsPVQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Xhue2TTs:rqcTsPVQ"
}
