Configuration Reference
Configuration Reference
Section titled “Configuration Reference”Bloom’s global settings live in a single HOCON file. Lure definitions and particle compositions are configured separately — this page covers the server-wide settings that affect all lures.
config/bloom/bloom.confGenerated on first startup with sensible defaults. Changes take effect with /bloom reload.
Global Settings
Section titled “Global Settings”| Field | Type | Default | Description |
|---|---|---|---|
debug | Bool | false | Enable debug logging and visualization |
notificationRangeMultiplier | Float | 4.0 | Multiplier applied to a lure’s range for notifications |
particleInterval | Int | 5 | Ticks between particle composition updates |
soundInterval | Int | 100 | Ticks between ambient sound checks |
notificationInterval | Int | 20 | Ticks between notification updates |
Example
Section titled “Example”debug = falsenotificationRangeMultiplier = 4.0particleInterval = 5soundInterval = 100notificationInterval = 20Settings Explained
Section titled “Settings Explained”debug
: Enables verbose logging and debug visualization. Run /bloom debug to toggle in-game. Useful for verifying lure ranges and targeting while building datapacks.
notificationRangeMultiplier
: Controls how far away players receive lure notifications. A lure with range = 10 and a multiplier of 4.0 notifies players within 40 blocks.
particleInterval
: How often particle compositions update, in ticks. Lower values mean smoother particles but more network traffic. Default of 5 (4 times per second) is a good balance.
soundInterval
: How often ambient sounds are checked and replayed. Default of 100 (every 5 seconds) keeps loops seamless without excessive sound packets.
notificationInterval
: How often lure notifications update for nearby players. Default of 20 (once per second).
Hologram Placeholders
Section titled “Hologram Placeholders”Holograms on placed and personal lures support these placeholders in hologram_lines and display_name:
| Placeholder | Resolves To |
|---|---|
{lure_name} | The lure’s display_name, or the item’s display name if using the default |
{owner} | The player who placed or activated the lure |
{time_remaining} | Remaining duration formatted as Xm Ys |
All hologram text supports MiniMessage formatting:
"hologram_lines": [ "<gold>{lure_name}", "<gray>Owner: <white>{owner}", "<yellow>{time_remaining}"]Display Behavior
Section titled “Display Behavior”Placed Lures
Section titled “Placed Lures”When a lure is placed in the world (right-click), it creates:
- Hologram above the entity, configured via
hologram_lines - Player head of the owner above the hologram (toggle with
show_owner_head) - Particles from the assigned particle composition
- Ambient sound if configured
Placed lures can be recalled by the owner with a double right-click within 3 seconds.
Personal Lures
Section titled “Personal Lures”When a lure is activated in personal mode (sneak + right-click), it creates:
- Hologram riding the player as a passenger
- Item display showing the lure item above the player
- Particles following the player
- Ambient sound following the player
- Action bar countdown timer visible to the owner
Personal lure state persists across disconnects and server restarts.
File Structure
Section titled “File Structure”config/bloom/├── bloom.conf # This file -- global settings└── particles/ # Particle compositions ├── grass_aura.conf ├── fire_blaze.conf └── electric_surge.conf
data/<namespace>/filament/item/ # Lure item definitions (JSON)Reload behavior:
bloom.confand particle compositions reload with/bloom reload- Lure item definitions reload with
/reload(Filament auto-reloads datapacks)
Next Steps
Section titled “Next Steps”- Creating Lures — Build custom lures in datapacks
- Particle Compositions — Design custom particle effects
- Installation — Requirements and setup