2.2.1
Compatibility
Changes
š Bug Fixes
Fixed: Dyed frames holding a map (fully or partially explored) showed the default fallback color instead of the actual dye color. Maps are large enough to sit almost exactly where the colored background is drawn, causing a depth conflict between the two. Fix: The colored background is no longer rendered at all when a frame holds a map. A map already fills the frame's visible area completely, so the tint wouldn't be visible anyway ā this removes the conflict entirely instead of trying to nudge the depth values further.
Notes
This affects maps only; regular items and empty frames are unaffected and continue to show their dye color normally. No config changes, no new controls ā this is a rendering-only fix.
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:fVuz4Kyd:kTl2HPHv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fVuz4Kyd:kTl2HPHv"
}

