Links
Tags
Creators
Details
1.5.1
Compatibility
Required content
Changes
Changelog
1.5.1
Fixed
- Box colours came out wrong under a resource pack. With the Modern style and a pack that recolours container GUIs, a red Shulker Box drew a purple card, a yellow one drew teal and a blue one maroon. Every colour taken from a pack had its red and blue swapped over.
- Cards were muddy and hard to tell apart. The colour was read from the slot squares instead of the panel around them, and packs keep slots much darker, so red sat next to brown and green next to lime. A card now takes the pack's panel colour and keeps a little of the box's own dye on top of it, so no two boxes look alike — including under packs that ship one GUI for all sixteen.
- Ender Chests borrowed a chest's colours. An Ender Chest opens the same screen as every chest and barrel, so under a pack that paints those wooden the Ender preview went wooden too. It keeps Better Shulker's own colours now, as it already did under the Vanilla style.
Internally, the panel sampler now reads the pack's panel rather than the slot band, and a client game test drives the four dyed previews under a real pack and checks each card against its dye.
The inventory screen also stops rebuilding a box's 27 stacks just to ask whether it holds anything, how full it is, or whether one more item would fit — it reads what the box stores directly. The three resource-pack caches drop their coldest entry when full instead of emptying themselves, so passing a chest of renamed boxes no longer throws away every panel it had already worked out. Neither changes what you see; both are covered by new game tests.
Optional dependencies
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:UUntxQ5e:pJ71I2I1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UUntxQ5e:pJ71I2I1"
}

