Tags
Creators
Details
4.0.1
Compatibility
Changes
If you want a server setup for the Lever Button Lights mod with zero effort, get a server with BisectHosting and receive 25% off your first month as a new customer using the code kreezxil
Changes
• Ported Lever & Button Lights 4.0.1 to Minecraft 26.3 on NeoForge.
• Added 16 colored Lever Lights and 16 colored Glass Light Blocks, for 51 lights in total, all in the Lever & Button Lights creative tab.
• The Glass Light Block is now the base ingredient: the Glass Lever Light is a stick above a Glass Light Block, and the Glass Button Light is one Glass Light Block.
• Colored lights are made by crafting any light of the same kind with a dye, and can be re-dyed. Silver uses light gray dye. The old stained-glass button recipes were removed.
• Fixed the clear Glass Button Light having no working recipe (issue #1).
• Button lights keep button-sized hitboxes (issue #2), and glass light blocks are selected as full blocks.
• Glass light blocks are now solid with full-block collision instead of walk-through.
• Added a config file (leverbuttonlights-common.toml) with light level on and off, redstone signal strength, hardness and explosion resistance for the lever lights, glass light blocks and button lights, plus optional redstone dust particles.
• Every option can be edited in game from the Mods list Config button, and a leverbuttonlights.example.cf file shows all options and defaults.
• Lights now use glass sounds and a hardness of 0.3 (light blocks 0.5) instead of breaking instantly; a pickaxe breaks them faster and no tool is required.
• Recipes unlock in the recipe book when their ingredient or dye is picked up.
• Renamed "Light_blue Button Light" to "Light Blue Button Light".
• Added a 512x512 mod logo to the mod list and rewrote the README.
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:gPWadOJp:nYcXTl0P"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gPWadOJp:nYcXTl0P"
}


