All versions
1.3.0
Release
RGB blocks 1.3.04 months ago 12
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Changes
Manual RGB Lighting Update
- Added server-synchronized AUTO and MANUAL RGB lighting modes.
- Added
/rgb autoand/rgb manualcommands. - Added
/rgb bakefor applying recorded RGB lighting changes in MANUAL mode. - Added
/rgb setbake <4-256>for selecting a player-centered Bake radius. - Added
/rgb setbake allfor processing all recorded dirty positions in the current dimension. - Added
/rgb getand/rgb bake getfor displaying the current mode, Bake scope, and world ID. - Added the RGB Light Switch item for toggling AUTO and MANUAL modes.
- Added the RGB Light Baker item for executing the currently configured Bake.
- Added a new RGB Tools creative tab containing both lighting control items.
- RGB Glow block and Chisels & Bits Glow bit changes are now recorded as persistent dirty positions while MANUAL mode is active.
- Bake requests now capture a fixed batch of dirty positions at the time the Bake begins.
- Changes made during an active Bake remain pending for the next Bake instead of extending the current batch.
- Dirty positions in unloaded chunks are preserved instead of being discarded.
- Switching from MANUAL back to AUTO now performs catch-up processing for loaded dirty positions.
- Added world-saved RGB mode, Bake scope, and world ID data.
- Added client-side, per-world and per-dimension persistence for RGB light sections.
- Added persistence for full-block RGB source positions.
- Added persistence for Chisels & Bits RGB source color and energy data.
- Added persistence for unbaked MANUAL dirty positions.
- Added backward-compatible loading of previous RGB lightmap formats and one-time source reconciliation.
- Reworked Chisels & Bits RGB source validation for newly created, changed, weakened, and removed Glow bits.
- Limited MANUAL Bake bootstrap and render rebuilding to sections associated with the selected dirty positions.
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:A48MxLWx:MYDsx0pc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:A48MxLWx:MYDsx0pc"
}

