Tags
Creators
Details
Licensed Apache-2.0
Published last year
Updated yesterday
All versions
1.2.0-fabric
Beta
BL: Accessories Layer v1.2.0+1.21.10 [Fabric/Quilt]9 months ago 286
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.10
Platforms
Fabric
Quilt
Supported environments
Client and server
Required content
Any compatible version
Changes
v1.2.0 — Render toggle & cosmetic slot support
New Features
- Render toggle support — pressing the visibility toggle button in the Accessories UI now hides/shows the BL lantern render
- Cosmetic slot support — placing a different lantern in the cosmetic slot now overrides the rendered lantern visual
v1.1.0 — Configurable accessory slots
New Features
- Added configurable slot support — modpack makers can now specify which Accessories slots accept lanterns via
config/bl_accessories_layer.json - Default configuration uses
["belt"]only, preserving full backward compatibility - Config file is auto-generated on first launch with default values
- Slot validation is handled via mixin — no manual datapacks needed for configured slots
- Removed hardcoded
belt.jsonitem tag in favor of dynamic validation
Bug Fixes
- Fixed lanterns stacking beyond 1 in accessory slots
v1.0.7 — Respawn reliability fixes
Bug Fixes
- Fixed race condition on NeoForge where Clone event handler could read belt slot before Accessories finished copying attachment data, potentially losing lamp state on death
- Fixed phantom lamp after respawn where mirror state could be restored without an actual item in the belt slot
v1.0.6 — Stability & compatibility improvements
Bug Fixes
- Fixed lantern disappearing when inventory is full — now drops at your feet
- Fixed lantern duplication/desync after death and respawn
- Fixed lantern state clearing during internal sync operations
- Fixed potential item duplication via mirrored state not being cleared on death
- Fixed
getBeltStackImplreturning non-empty Optional with an empty ItemStack - Fixed NeoForge reload listener registration causing potential crash on startup
- Fixed duplicate
no_rendererregistration producing error logs on resource reload
Improvements
- Added defensive try-catch for Fabric reload listener registration
- Added
accessoriesas a required dependency in mod metadata (Fabric & NeoForge) - Migrated from Architectury Loom to Multiloader build system
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:geZ7ilkE:2kNmRzlh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:geZ7ilkE:2kNmRzlh"
}

