Tags
Creators
Details
Licensed ARR
Published 4 months ago
Updated 3 days ago
All versions
1.5.2
Release
Contraption Lights 1.5.2last month 4,100
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Server-side
Changes
- A light on a Sable sub-level colours the sub-level's own blocks again instead of lighting them white. The same fix applies to the world when Sodium is not installed.
- Create shafts, cogs and other Flywheel-rendered blocks near a light no longer sometimes stay white instead of taking its colour.
- Switching coloured light on while in a world now colours the light moving structures cast, instead of leaving it white until the world is rejoined.
- Snowlogged blocks from Snow! Real Magic!, and other blocks drawn through the Fabric renderer, now take the colour of nearby lights when Sodium is not installed.
- Server light blocks no longer delete a block or water placed where one of them stood, and no longer remove light blocks placed by players.
- Server light blocks on Sable sub-levels are much lighter on server performance when blocks on a sub-level change.
- Server light blocks now light up underwater and in carved caves.
- A Create contraption that has not moved yet now places its light blocks.
- Server light blocks on Create bearings, pistons and gantries keep up with the moving build instead of trailing a tick behind it.
- Nearby lights now share light blocks, so fewer are placed. New server options
lightBlockMergeToleranceandmaxLightBlockChangesPerTick. - A light inside a sealed room on a Sable sub-level no longer places a light block in the world outside. New server option
enableSubLevelLightBlockOcclusion. - An error in server light blocks now removes the ones already placed and stops only that dimension until it reloads.
- Players who also run the mod with coloured light on now see server light blocks in their source's colour instead of a warm glow.
- Servers with Sable no longer slowly build up memory from sub-level block changes while sub-level light blocks are off.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
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:gUdYw8o3:LPyT3Oik"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gUdYw8o3:LPyT3Oik"
}

