Links
Tags
Creators
Details
All versions
0.8.0
Release
Celeritas/Actinium Extra 0.8.03 weeks ago 123
Compatibility
Minecraft: Java Edition
1.12.2
Platform
Forge
Supported environments
Client-side
Changes
0.8.0
Added
- Actinium support with automatic renderer detection and shared configuration.
- Settings search and filtering, Ctrl+F shortcut, and Shift + scroll slider adjustment.
- Collapsible mod categories in the Celeritas settings sidebar.
- Memory usage overlay.
- Sign text and item-frame map back-face culling.
- Configurable entity and tile entity render distances.
- Per-particle spawn percentages.
- Separate sun and moon toggles.
- Per-dimension fog settings.
- Menu, unfocused, and minimized FPS limits.
Changed
- FPS statistics now display average FPS, 1% low, and 0.1% low.
- Reorganized settings into ten category pages.
- Updated localization and aligned translation keys with upstream projects.
- Actinium uses its integrated settings frontend, search, and mod-category folding.
- Duplicate cloud and menu FPS controls are hidden when using Actinium.
Fixed
- Corrected item-frame LOD, including Forge emissive rendering and Actinium's fast item rendering path.
- Fixed crashes when adjusting sliders with Shift + scroll.
- Preserved pending settings while searching or collapsing mod categories.
- Prevented camera-based culling and fog overrides from affecting Iris shadow passes.
- Fixed the search cursor position during text selection.
- Fixed FPS statistics with negative monotonic clock timestamps.
- Fixed early configuration loading to use the correct game directory.
Requirements
- Cleanroom Loader
- Java 25
- Celeritas or Actinium
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:chDXcLjd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LXQekDcE:chDXcLjd"
}

