Tags
Creators
Details
Licensed ARR
Published 4 months ago
Updated 3 days ago
All versions
1.1.0
Release
Contraption Lights 1.1.03 months ago 948
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Server-side
Changes
- On LAMB mode, a Sable sub-level's carried lights now light separate Create contraptions and stationary kinetics, and a contraption's carried lights now light stationary kinetics.
- On LAMB mode, a Create contraption riding a Sable sub-level is now lit by world sources, separate sub-levels, and static world blocks at the position it is actually drawn (its host sub-level already lights it).
- On LAMB mode, a Create contraption riding a Sable sub-level now lights its host sub-level, the surrounding world, separate sub-levels, and stationary kinetics with its own carried lights, tracking its motion.
- Fixed a crash on load when
modewas LAMB without LambDynamicLights installed. A selected backend whose mod is not installed now switches the mode to OFF instead of crashing or silently doing nothing. enableWorldToContraptionLambLightandenableWorldToKineticLambLightare much lighter on performance near lit sub-levels and contraptions carrying many lights.enableWorldToStructureVeilLight(Veil, non-shader) is lighter on performance.- Running
enableWorldToSubLevelLambLightandenableWorldToContraptionLambLighttogether near a Sable sub-level that carries a contraption no longer tanks the frame rate; both on now costs about the same as either one.
Optional dependencies
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:Tc6h7no9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gUdYw8o3:Tc6h7no9"
}

