Tags
Creators
Details
Licensed MIT
Published 8 months ago
Updated 4 months ago
All versions
0.1.0-beta3
Beta
Toggle Beacon Beams v0.1.0-beta38 months ago 64
Compatibility
Minecraft: Java Edition
1.21.11
Platforms
Fabric
Quilt
Supported environments
Client and server
Changes
Toggle Beacon Beams 0.1.0-beta3
- Bump version and some code cleanup. Last beta build before 0.1.0 release. Just gotta add a README, custom sprites, and get NeoForge truly supported (Also, I may have missed some things, this was a big changelog)
- Config screen adjustments:
- Added a new config flag modEnabled so the mod (UI button + hidden beam suppression) can be enabled/disabled from the config screen on singleplayer
- Dropped "On" and "Off" button components in favor of individual conditional "showAll" and "hideAll" config buttons
- Attempting to access the config screen returns client to game on servers, and disables the config screen server-side
- Fixed some client-server desync issues, notably:
- Fixed beacon screen toggle-state desync while moving, since BeaconScreen now captures the beacon block position on init and keeps reading hidden state from that fixed position. This prevents our custom UI button from getting stuck on one state while client position is moving outside the screen
- New fallback to re-acquire the beacon position so state lookup is resilient
- Fixed a multiplayer-only beacon click issue by switching beacon UI clicks back to using TOGGLE_BEAM_BUTTON_ID when connected to multiplayer, while still keeping explicit HIDE/SHOW IDs in singleplayer. This avoids hide/show mismatch on servers.
- Updated the toggle action itself to compute hide/show from current world stat before applying changes, keeping behavior aligned with the label
- Fixed some naming conventions leftover from original name, Let There Be Light:
- Changed serialization key to tbb_hidden from original ltbl_hidden
- Fixed the config .json from being incorrectly labeled handsoffmyblock, the name of my other mod which I copied the same config manager from, to tbb.json :/
- Added new and updated translations
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:yNgWU1sr:8sxm6H4y"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yNgWU1sr:8sxm6H4y"
}

