Links
Tags
Creators
Details
Licensed MIT
Published 6 months ago
Updated 2 days ago
All versions
2.0.0+26.3
Release
Shulker Palette 2.0.0+26.32 days ago 24
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
2.0.0
Shulker Palette is rebuilt for Minecraft 26.3.
Added
- Three new modes alongside random by count: equal random, pick, and gradient.
- A column of buttons on the shulker box screen to turn the palette on or off, switch modes, and save or load the palette.
- The palette modifier key, Left Alt by default and rebindable. Holding it lets you scroll through picks and gradient rows, place the shulker box itself, or open the shulker box in your hand.
- The next block shows inside the box in your hotbar and in your hand, and a view of the box appears above the hotbar while you scroll.
- Repaint, in creative, which replaces the block you're looking at with the palette's next block.
- Save and Load through the clipboard, as text you can edit. Loading in survival adds a cheat sheet that shows which blocks go in each slot.
- A palette box keeps its palette when it's broken.
- Toggle palette and Toggle repaint keys, both unbound by default.
Changed
- Requires MenuKit 7.2.0 or newer and SlotKit 1.1.0 or newer.
- Needed on both the client and the server.
- Palettes from 1.0.0 don't carry over. The blocks inside stay where they are, and one click on the box's power button, or the Toggle palette key, makes it a palette again.
- The Inventory Plus peek toggle is removed, since Inventory Plus no longer has a peek view.
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:sfVmg2YT:vA4Pwb2o"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sfVmg2YT:vA4Pwb2o"
}

