All versions
8.0.7
Release
v8.0.75 months ago 704
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Fairy Lights 8.0.7 - Connection Placement & Item Drop Fixes
Major Fixes
Connection Placement System
- Fixed placement after breaking: Hanging lights can now be placed at different distances after breaking the first fastener. Previously, the connection would remain in the player's hand and block new placements.
- Fixed reconnection logic: When placing a connection at a different distance, the system now properly handles reconnecting to a new destination or creating a new connection if the old destination is invalid.
- Improved connection validation: The placement system now correctly ignores removed or invalid connections, allowing new placements even when stale connection data exists.
Item Drop System
- Fixed swapped light drops: When breaking a hanging lights connection, all individual lights from the pattern (including any lights you swapped in) are now properly dropped as items. Previously, swapped-in lights would be lost.
- Fixed drop behavior: Pattern items are now dropped both when manually disconnecting a connection and when breaking the fastener block, ensuring you always get your lights back.
Technical Improvements
- Enhanced connection type matching to allow reconnection when types match
- Improved handling of stale connections in player capability
- Better null safety checks in connection removal code
- Fixed item dropping to occur in both
onRemove()anddisconnect()methods
Notes
- Breaking a hanging lights connection now returns all lights that were placed in the pattern
- You can now freely place connections at different distances without being blocked by previous placements
- The connection system now properly cleans up invalid connections automatically
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:BC84wYkA:zYIEL06e"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BC84wYkA:zYIEL06e"
}