Tags
Creators
Details
2026.7.0
Compatibility
Changes
FEATURES
-
Configurable Element Toggles: Added new toggle options inside
config.ymlto completely control the visibility and loading of standard colors, gradients, and patterns. -
Dynamic Content Loading: Rewrote the color engine to conditionally load elements depending on your active config settings, reducing unnecessary memory allocation.
-
FIXES & IMPROVEMENTS
-
Automatic Config Self-Healing: Implemented a failsafe mechanism that automatically re-adds any missing keys or sections to
config.ymlwithout overriding your existing settings. -
Enhanced Performance: Optimizing configuration checks ensures smoother server startup times when parsing active formatting modules.
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:HIEZ98Xn:5fzKiMri"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HIEZ98Xn:5fzKiMri"
}

