All versions
1.0.6
Release
Lampcrafting 1.0.62 years ago 95.6K
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
Update 1.0.6: Additions:
- Added three patterns - “Butterfly”, “Wind”, “Bow”, “Crossknit” and “Cartofedstone”, also their versions for shower lamps
- Added a lamp with a mechanic - “Light Changer”, the essence of the mechanic is simple, it simply shines with the same intensity of light as the redstone power fed to it
- Added an achievement related to the light changer lamp
- Added one secret lamp Changes:
- One secret team now has limited access rights(max level)
- The soul lamps are now in the “piglin_repellents” tag, making the lamps repel pyglin like the soul torch or the soul bonfire(previously they were repelled by the homemade method)
- Improved the texture of the inside of large redstone lamps
- Changed the balance of one secret lamp
- Minor changes: Now the player also gets the achievement “Live Long and Shine Long” for a regular lamp. Fixes:
- Fixed that when placing a lamp block near a redstone source, for the “Flat” pattern lamp, the minimum redstone power level to turn on was 2 or higher
- Fixed that it was possible to grab enabled versions of colored lamps in creative via the middle mouse button's block picker function
- Fixed that the achievement “Ginny what are you doing here?” could only be obtained by crafting a redstone soul lamp with a vanilla redstone soul lamp texture. Now this achievement can also be obtained by taking any patterned soul lamp in your inventory
- Fixed that lamp sounds were in the “neutral” category, they are now in the “blocks” category
- Recipes for lamps will now be unlocked when getting some achievements. This was not the case before, so their crafting was not displayed in the recipe book
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:Ec2eBEYf:NGKSkqdp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ec2eBEYf:NGKSkqdp"
}

