Links
Tags
Creators
Details
Licensed LGPL-3.0-only
Published 2 months ago
Updated 1 hour ago
All versions
0.6.1
Beta
Pulsar Lighting Engine 0.6.12 weeks ago 23
Compatibility
Minecraft: Java Edition
1.12.2
Platform
Forge
Supported environments
Client and server
Changes
[0.6.1] - 2026-10-31
Added
- Add RGB source-color presets for end rods and magma blocks.
- Add Future MC lantern, soul lantern and campfire colors, preserving their original light levels and lit/unlit behavior.
- Add source-color presets for Thermal Foundation, Thermal Expansion, BuildCraft, Railcraft, Forestry, BiblioCraft, OpenComputers and Galacticraft.
- Add a glowstone-colored preset for Extra Utilities 2's glowing glass variant. Other decorative glass variants retain their existing behavior.
Changed
- Align vanilla and supported mod source hues with SuperNova, including glowstone, jack o'lanterns, portals, lanterns and Botania's blaze block. Preserve contextual brightness, mod-provided color APIs and user overrides.
- Match SuperNova's dim dye palette rounding for Botania buried petals and mushrooms without changing their contextual light levels.
- Soften dim RGB hues while retaining absorbed color channels at zero. Genuine skylight and other light sources can still mix with filtered light.
Fixed
- Prevent Celeritas from borrowing sky or block light through closed stair and slab faces, fixing light leaks around carpets and flowers underneath them (#20).
- Prevent non-legacy RGB tinting from adding white components back to light filtered through colored glass. Apply the same correction to the generic shader lightmap bridge.
- Correct the OkLab forward transform to match its inverse, preventing hue shifts in isolated primary colors.
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:gs7RbryI:znNNqnfm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gs7RbryI:znNNqnfm"
}

