Tags
Creators
Details
Licensed LGPL-3.0-only
Published 5 years ago
Updated 2 weeks ago
All versions
2.2.1-a-1.21.1
Alpha
2.2.1-a - 1.21.1 neo/fabric2 years ago 1.4M
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platforms
Fabric
NeoForge
Supported environments
Client-side
Server-side
Client and server
Changes
Highlights:
- Added a option to toggle cloud rendering
- Added nearby beacon culling to prevent overdraw
- Fixed LOD Lighting
- Fixed DH Cloud colors
- Fixed LODs flashing when loading/unloading
- Fixed Lithium breaking DH world gen for MC 1.20.1 and older
Full Changelog
Additions:
- Add a top level UI config to toggle cloud rendering
- Add nearby beacon culling
- Enabled by default, can be disabled under advanced graphics
Changes:
- Change delayed LOD modified save from 2 seconds -> 500 ms
- This should make LODs appear to update slightly faster
- Allow users to re-enable the DH renderer if an exception is thrown
- To re-enable the renderer, toggle DH rendering using the UI config menu
Bug Fixes:
- Fix LODs not updating in the nether or when blocks are changed underground
- Note: DH only listens for some block changes underground (currently 1 in 4 blocks), so changing several blocks or one light emitting may be necessary to trigger an update).
- Fix Lighting not generating correctly
- Fix DH clouds colors not matching vanilla MC clouds
- Fix glass panes not affecting beacon colors
- Fix several beacon rendering/updating issues when beacons are on chunk borders
- Disable instanced rendering on Mac when Sodium is present
- This should fix M1 macs crashing when both DH and Sodium are together
- Fix LODs flashing when they load/unload
- Fix Lithium breaking DH world gen for MC 1.20.1 and older
API Changes
Bug Fixes:
- Fix RenderableBoxGroup not supporting .clear()
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:uCdwusMi:pEvLEY5E"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uCdwusMi:pEvLEY5E"
}

