Links
Tags
Creators
Details
Licensed LGPL-3.0-only
Published 2 months ago
Updated 1 hour ago
All versions
0.6.5-beta
Beta
Pulsar Lighting Engine 0.6.5-beta1 hour ago 3
Compatibility
Minecraft: Java Edition
1.12.2
Platform
Forge
Supported environments
Client and server
Changes
Changed
- Update CleanroomDevEnv to
6b24e5c, with Kotlin DSL build scripts and parallel configuration caching. Native compatibility tests support configuration caching; the standalone API publication and production JAR checks remain available. - Apply version tokens to all compiled classes and check class constant pools for unresolved tokens, avoiding false matches in binary data.
- Select JVM runtime variants when resolving embedded dependencies.
- Move Spotless profiles to
gradle/spotlessand extend Renovate dependency coverage. - Validate release-note extraction and retain support for resuming interrupted uploads. GitHub Releases continue to use the pre-release flag disabled.
- Add LGPL-3.0-only source headers while preserving upstream copyright notices and the CleanroomDevEnv MIT notice. The API publication declares its LGPL license.
Removed
- Remove Actinium-specific renderer integration. Actinium targets Cleanroom 0.6.x; Pulsar requires Cleanroom 0.7.14-alpha or newer within the 0.7.x series.
- Remove Felt build tooling and its header-management configuration.
Fixed
- Respect closed outgoing block faces during SCALAR and RGB light recalculation, avoiding false mismatches and unnecessary relighting at chunk boundaries near slabs and other sided blocks.
- Release completed tasks and their chunk references from stale priority indexes when a lighting queue drains.
- Clear partially initialized engine caches after setup failures, so reused engines do not retain stale chunk data.
- Reject invalid saved light-nibble states on load, allowing corrupt caches to relight before they can cause errors on later saves.
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:npMl6XHQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gs7RbryI:npMl6XHQ"
}

