Links
Tags
Creators
Details
0.6.0
Compatibility
Changes
New Features
-
Sky Colors — new toggle to apply or disable biome-based sky coloring (Details).
-
Advanced Item Tooltips — always show an item's id and durability, without needing the F3+H toggle (Extras).
-
Toasts — master toggle plus per-type control for advancement, recipe, tutorial, and system popups (Extras).
-
Item Frame LOD — beyond a configurable distance, framed 3D (block) items render with only their front/back faces and framed maps are hidden, lightening walls of far-away frames while keeping the frame border and name tag. New Item Frame LOD Distance slider (0 = off, 0–256 blocks) (Render).
Improvements
-
Reworked several option controls to fit better:
-
Cloud Scale now displays as a 0.25×–1.00× multiplier instead of a raw 1–4 value.
-
Dependent sub-options now grey out live when their parent is disabled (fog / clouds / particles / animation sub-toggles, extended FPS, steady-HUD refresh interval, beacon beam height, item-frame name tag, star count).
-
Added unit labels (blocks / ticks) and performance-impact hints (cloud distance, star count).
-
-
Simplified the fog controls: removed the redundant Fog Type cycler, keeping a single Fog toggle.
Bug Fixes
-
Protected gameplay fog — turning fog off or changing its distance no longer strips gameplay-critical fog (blindness, underwater, lava).
-
Hide HEI Until Searching — the hidden item list is now fully inert: it no longer draws, shows tooltips, or opens the recipe viewer when you click the now-empty area.
Localization
- Fixed machine-translated, inaccurate, and inconsistent strings across
Compare
Full Changelog: https://github.com/Sumire-Labs/Celeritas-Extra/compare/0.5.1...0.6.0
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:LXQekDcE:B2K8HQlI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LXQekDcE:B2K8HQlI"
}

