Tags
Creators
Details
Licensed ARR
Published 4 months ago
Updated 3 days ago
All versions
1.5.0-beta.4
Beta
Contraption Lights 1.5.0-beta.42 months ago 130
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Server-side
Changes
- A resource pack can now give a block a light colour that cycles, with
"color": "rainbow"or a cycle of colours and a period of your own. NewanimatedLightColorssetting turns it off. - Small Sable physics contraptions no longer stay unlit when a light is right beside them.
- Light no longer reaches a Sable physics contraption through solid blocks, whether from a block it rests against or from a source sealed away under the floor.
- Fixed a crash with mods that read the light level at a position while coloured light is on, such as Wakes.
- Particles within 8 blocks of a Sable physics contraption now take the colour of the light on them instead of staying white.
- Torch flames, glow squid sparks, portal particles and nautilus shell particles now take the colour of the light on them instead of staying white.
- Create kinetics and other Flywheel-rendered blocks placed in the world now take the colour of the light on them.
- Lights that change colour without changing brightness, such as swapping one coloured lantern for another, now recolour Sable sub-levels right away instead of only after you moved.
- Fixed blocks and particles inside a Sable physics contraption keeping the colour of a light you were holding earlier.
- Fixed the sky light on blocks and particles inside a Sable physics contraption while coloured light is on.
- Mobs and players now take the colour of the light on them with Entity Texture Features or Entity Model Features installed, instead of staying white.
- Sealed rooms inside a Sable sub-level now block the light on mobs and players with Entity Texture Features or Entity Model Features installed.
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:7tuiBSU0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gUdYw8o3:7tuiBSU0"
}

