Tags
Creators
Details
All versions
1.1.0
Release
SmartShulkers 1.1.02 days ago 10
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
Platforms
Paper
Purpur
Changes
- Added a blacklist to every shulker. Left click with an item still edits the whitelist, right click now edits the blacklist. A shulker with only a blacklist takes everything except the listed items
- Added a way to edit filters without the inventory screen, which sorting mods can trigger by accident (#11): hold the shulker in your off hand and the item in your main hand, sneak and left click the air for the whitelist or right click the air for the blacklist
- Both filter methods have a toggle in
settings.general.filter-methods, so servers with sorting mods can turn off inventory clicking - Fixed shulker boxes not being craftable with anything but SmartShulkers' own recipes, vanilla dyeing works again (#11). Dyeing a Smart, Garbage or Sell Shulker keeps its type, filter and contents
- Garbage and Sell Shulkers now keep their contents when they are crafted from a filled shulker box, before only Smart Shulkers did
- A shulker that is already a Smart, Garbage or Sell Shulker can no longer be run through a conversion recipe again
- Fixed picking up part of a stack into a Smart Shulker still giving you the whole stack, which duplicated items
ignore-items.namednow understands the/regex/iform shown in the config, plain entries are matched case insensitively against the plain item name- No longer rewrites
config.yml(and strips its comments) when Vault is missing, sell shulkers are just inactive - The three identical revert recipes per shulker color are now a single one
- Verified on Paper up to Minecraft 26.3
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:zSjTFZZN:x2MU12lB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zSjTFZZN:x2MU12lB"
}

