All versions
7.3.0
Beta
Glow Sticks 7.3.02 months ago 515
Compatibility
Minecraft: Java Edition
26.2
Platforms
Fabric
Quilt
Supported environments
Client and server
Required content
Any compatible version
Changes
Changelog for Glow Sticks
All notable changes to this project will be documented in this file.
Note
This change log includes the summarized changes. For the full changelog, please go to the GitHub History instead.
v7.3.0
- Fixed #5 by adding vertical placeable creative glow sticks.
- Fixed #6 by adjusting the Japanese Name for "Glow Stick". Thanks a lot to
@looksky495for the detailed explanation. - Fixed temporary underwater light blocks to restore water correctly after expiring.
- Fixed waypoint particles for white glow sticks when no glow stick was held.
- Added config value validation for particle spawn rate and other glow stick settings.
- Improved tooltip texts and configuration handling for glow sticks.
v7.2.0
- Refactored code for better readability and maintenance.
- Fixed #2 by adding distance requirement.
- Fixed onUseTick method to prevent crashes.
- Added japanese translation, thanks to
@PExPE3. - Added creative versions of the Glow Sticks which do not despawn.
- Added powered versions of the Glow Sticks which reactivate when powered by Redstone.
- Added additional 3 variants for normal and creative Glow Sticks.
- Removed
despawnEnabledconfig entry and replaced it withdespawnTicks=0configuration option.
v7.1.0
- Added basic particle effects for the Glow Sticks.
- Added waypoint feature which shows a waypoint to the player when holding a Glow Stick and sneaking.
- Added a new configuration option.
v7.0.0
- First release of reworked Glow Sticks mods for Fabric, Forge and NeoForge.
- General Code optimizations and improvements.
Optional dependencies
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:pr7UDXB2:pMkuZSla"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pr7UDXB2:pMkuZSla"
}

