Links
Tags
Creators
Details
0.6.0+1.21.1
Compatibility
Required content
Changes
Version 0.6.0+1.21.1
Major Quality-of-Life Update
Revamped Configuration Screen

- Added a "Blur Duration" slider for easily fine-tuning smooth blur
- Added a "Background Dimming in Containers" slider (default value: 20%; vanilla value: 75%)
- Replaced wide individual screen settings buttons with new rows that are easier to navigate and feature a subtle hover animation
- Added a quick search bar for screens! Furthermore, the screen list now remembers and restores both your scroll position and search query when returning from sub-config menus
Updated Data Storage Format
Schema version has been updated to 3. Key changes:
- All keys and their values are now written in
snake_case - Animation profile properties have been renamed for consistency:
offset->initial_offsetstartScale->initial_scalestartAlpha->initial_alpha
⚠️ Important note on config migration
Config files will migrate to the new schema version automatically upon launch, preserving your existing settings. However, backward compatibility is not supported (older mod versions cannot read the new schema). It is highly recommended to back up your config file if you plan to downgrade and wish to keep your custom settings.
Improved Background Blur & Dimming
- Fixed missing smooth background animation in the Creative Inventory screen
- Fixed redundant background dim animations when switching to a screen (which was unlisted or disabled in the config) if the previous screen was already blurred and dimmed
- Background animation now applies to all in-game screens
Added New Screen Animated by Default
- Open Link confirmation screen
Other Fixes & Improvements
- The Creeper face is back on the letter 'A' in the logo!
Don't ask where it went...
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:zS8uflwP:Xr8TCfLF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zS8uflwP:Xr8TCfLF"
}

