Links
Tags
Creators
Details
0.10.0
Compatibility
Changes
Important Notice
Celeritas/Nothirium Extra 0.10.0 supports only Cleanroom 0.7.11 or later. If you are using Cleanroom 0.6.x, please use version 0.9.x.
For now, we have fully transitioned to Cleanroom 0.7.0 in version 0.10.0, but we still plan to release updates for Cleanroom 0.6.x users as needed.
Added
- Added an experimental static item vertex cache, disabled by default. It reuses vertex output for supported static item geometry while retaining Forge lighting and item-frame LOD. Performance gains vary by system and scene.
- Bounded the experimental cache to 256 entries and 4 MiB of vertex data. Dynamic geometry, registered item color handlers, Iris, and detected native renderer item caches use the normal rendering path.
Changed
- Migrated the build to CleanroomGradle 0.22.1 and Cleanroom 0.7.11-alpha USERDEV, adapting Sumire-Labs/ModTemplate's cleanroom branch while retaining renderer adapters and release checks.
- Updated Gradle to 9.8.2, Cleanroom Versioning to 3.4.0, CleanMix to 0.7.4, and MixinExtras to 0.5.5.
- Use Cleanroom's SDL APIs directly for window controls and IME integration.
- Cache sprite animation categories, unchanged HUD text, and render-distance exemption checks.
- Reuse frame-statistics buffers and select the slowest percentile without sorting the full sample history.
- Avoid profiler name lookups when profiling is disabled, and close profiling scopes reliably.
- Calculate sign-text visibility once per render and cache filtered static item-frame LOD geometry.
- Cache particle policies and skip constructing known vanilla particles when their configured spawn rate is zero. Custom particle factories retain the normal discovery path.
- Clear item geometry caches when models are reloaded.
Removed
- Removed the Cleanroom 0.6.x GLFW compatibility backend and reflective SDL compatibility helpers.
- Removed migration of the legacy combined
sunMoonsetting. Existing separatesunandmoonsettings remain supported; the obsolete key is removed when loading the configuration.
Fixed
- Preserve vertex-buffer position and limit when capturing experimental item-cache entries, preventing corrupted item rendering.
- Verify production Mixin mappings, the supported loader range, and the absence of references to the removed GLFW backend in release artifacts.
- Exclude development MCP JARs from GitHub release uploads.
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:MO8YTNE8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LXQekDcE:MO8YTNE8"
}

