Links
Tags
Creators
Details
0.5.6
Compatibility
Changes
v0.5.6 Release Notes
๐จ Lossless HEX Colors & MiniMessage Tag Engine Issue: When players created tags using HEX codes (e.g., &#ff0000), gradients, or MiniMessage formats via /clan tag, the colors were being downsampled to the nearest standard Minecraft legacy color, ruining smooth gradient transitions.
Fix: Implemented a custom legacySectionSerializer that prevents Kyori Adventure from downsampling colors and converts HEX/MiniMessage formats flawlessly without quality loss.
Updated Files: ChatUtils, PlaceholderProvider, ClanChatEvent, ClanAllyChatEvent, ClipPlaceholder, and ClanSetTagCommand.
๐ข Full MiniMessage & HEX Support for Server Announcements Issue: Broadcast messages sent during clan creation and deletion (announcements.create and announcements.delete) were not parsing MiniMessage syntax or custom HEX colors properly.
Fix: Announcements are now formatted into Adventure Component objects via ChatUtils.formatMiniMessageWithLegacySupport and delivered losslessly to online players using ChatUtils.sendComponent.
Updated Storage Adapters: YAML, SQL, MongoDB, and Redis.
โ๏ธ Fixed Announcement Fallback Glitch Issue: Database handlers initialized prior to langManager being instantiated at startup caused local references to remain null. This forced announcements to fall back to hardcoded English strings instead of reading from custom language configuration files.
Fix: Replaced static field references with a null-safe getLangManager() accessor method across all storage providers (YAML, SQL, MongoDB, Redis), ensuring custom localized messages are always resolved correctly.
๐ ๏ธ Bug Fixes & Stability: Resolved all color downsampling, broken gradient rendering, and localization configuration issues reported via Discord.
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:KqVaHdNX:D9xqvyKd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KqVaHdNX:D9xqvyKd"
}
