Links
Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated 2 days ago
All versions
5.2.0+1.21.11
Release
LootBeamsUp 5.2.0+1.21.11 NeoForge2 days ago 11
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.11
Platform
NeoForge
Supported environments
Client-side
Changes
LootBeamsUp 5.2.0 for Minecraft 1.21.11
New in 5.2.0: server rules
- A server can limit LootBeamsUp on its players' clients with its resource pack: one file,
assets/lootbeamsup/data/restrictions.json, switches off whole features (particles, light, post effects, nametags and more) and forces or limits single settings, for example "beam height at most 4" or "render distance 8–64". - Your own settings are never changed. The server's rules apply on top while its pack is loaded; when you leave, everything looks as you set it again.
- In the Configuration editor a lock in front of a setting shows that the server restricts it; its tooltip says how. You can still edit the setting: it changes your own value.
- The Compatibility screen lists the active server rules and tells you once in chat.
- Pack authors: the file format, the setting ids and the feature list are documented in the mod's repository (
docs/server-restrictions.md). Broken parts of the file are skipped and logged, the rest still applies.
Fixes in 5.2.0
- A VFX material whose shader fails to compile no longer crashes the game when an animated effect uses it.
Fixes in 5.1.2
- Items carrying a malformed or extreme
lootbeamsup_config(item NBT a server or a creative-mode player can set) could crash or freeze every client near the item. Such settings are now checked: invalid ones are ignored, numbers are kept within the ranges the editor allows, and effect lists are limited. - Particle emitters with an extreme rate could freeze the game. Spawning is now capped.
- An item id from a removed mod in the item whitelist or blacklist, or an invalid tag in a selector, crashed the game every frame. Such entries now simply match nothing.
- Items with hidden tooltips (common in server menus) crashed when a labelled item group matched them.
- One broken
.objmodel in any mod or resource pack made resources fail to load. Broken models are now skipped and logged, and models are loaded only when used. - A VFX material whose shader does not compile no longer fails the whole resource reload.
- Memory was not released after leaving a world or changing dimension.
- Fixed a rare case where effects kept drawing into the wrong target after a renderer mod skipped a pass.
- Better compatibility with other mods that change terrain rendering.
Other in 5.1.2
- The
/lootbeamsdeveloper commands are no longer available outside a development environment; everything they did is in the in-game editors.
Optional dependencies
Any compatible version
Any compatible version
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:fFPOjWlN:yFRDINal"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fFPOjWlN:yFRDINal"
}

