6.7.0
Compatibility
Changes
๐ฆ LightAura v6.7.0 - Configuration System Overhaul
๐ง Config System Redesign
Reorganized the entire configuration into structured categories: Performance PlayerLighting DroppedItemLighting WorldInteraction Visual Debug Introduced configVersion for tracking and auto-upgrading outdated configs.
๐ New Config Features
Performance Added maxLightSources to limit active dynamic lights. Added enablePerformanceMode to reduce feature load for low-end systems. Configurable performanceModeRadius. Player Lighting Added fine control: enableHandPositionLighting enableEyePositionLighting animationBrightnessMultiplier Dropped Item Lighting Added enableDistanceScaling and minDistanceMultiplier. New enableItemBobbingSync for synced lighting with item animations. World Interaction New options: enableWaterLighting enableLavaLighting respectLightBlockingBlocks Introduced block blacklist (e.g., bedrock, barrier, etc.). Visual Added smooth transitions and flicker effects: enableSmoothTransitions transitionSpeed enableFlickerEffect flickerIntensity Optional enableColoredLighting (experimental). Debug Added advanced debug settings: enablePerformanceMetrics showLightPositions logFrequency
๐ก Light Items System
Light items are now mapped with lightItems.minecraft:item=light_level. Added many new default light-emitting items, including: nether_star, sculk_catalyst, glow_item_frame, and more. New utility methods: addLightItem(itemId, lightLevel) removeLightItem(itemId) reloadConfig() Light levels are validated (range: 0โ15).
๐ Other Improvements
Validation system for numeric config values to prevent invalid inputs. Auto-regeneration of outdated configs with updated comments and defaults. Enhanced logging when debug mode is enabled.
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:MNQ8PfgX:YPCd6igC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MNQ8PfgX:YPCd6igC"
}

