# Broadcast++<\/p>\n
**The modern broadcast plugin for Minecraft servers.** One YAML file for every announcement across chat, titles, action bars, boss bars, and multi-channel scenes \u2014 on Paper, Spigot, Velocity, and Folia.<\/p>\n
—<\/p>\n
## What is Broadcast++<\/p>\n
A single, unified primitive \u2014 **scenes** \u2014 runs every automated or triggered broadcast on your server. A scene has one trigger (join, interval, daily, or manual) and one or more steps. Each step can fire multiple channels at the same instant or chain them on a timeline. Drop the jar in, edit one line, `\/bc reload`, done.<\/p>\n
—<\/p>\n
## Why server owners pick it<\/p>\n
– **One primitive for everything.** Stop juggling `welcome.yml`, `rotation.yml`, `schedule.yml`. Every broadcast is a scene with the same shape.
\n– **Auto-brand your broadcasts.** Set `server-name:` once; every chat broadcast gets a gradient prefix. Change `server-color:` to restyle \u2014 no MiniMessage knowledge required.
\n– **Animated boss bars.** Drain or fill the bar over a duration as a visual countdown. No custom scheduler code.
\n– **Proxy-aware.** On Velocity, filter scenes by backend with `servers: [lobby]` to target broadcasts per-server.
\n– **Reload-safe.** `\/bc validate` dry-runs your config before applying. If the new config has errors, the old one stays live.
\n– **Plug-and-play.** Ships with five working presets and three working scenes. Useful on boot with zero edits.<\/p>\n
—<\/p>\n
## Scenes \u2014 one primitive for everything<\/p>\n
“`yaml
\nscenes:
\n welcome-sequence:
\n description: “On-join cinematic”
\n on-join: true
\n steps:
\n – { at: 0s, chat: welcome }
\n – { at: 1s, actionbar: tip-spawn }
\n – { at: 3s, title: welcome-back }<\/p>\n
chat-rotation:
\n every: 5m
\n cycle: true
\n steps:
\n – { at: 0s, chat: tip-sethome }
\n – { at: 0s, chat: rules }
\n – { at: 0s, chat: discord }<\/p>\n
daily-reset:
\n daily-at: “00:00”
\n steps:
\n – { at: 0s, chat: server-restart }
\n“`<\/p>\n
### Triggers \u2014 pick one per scene<\/p>\n
| Trigger | Fires | ### Filters \u2014 gate delivery per-audience<\/p>\n “`yaml All filters are optional. Set at scene level (applies to every step) or at preset level (applies just to that preset). When both are set, the stricter value wins.<\/p>\n ### Timeline vs. cycle<\/p>\n – **Timeline (default)** \u2014 every step fires at its `at:` offset from scene start. —<\/p>\n ## Branding in two lines<\/p>\n “`yaml That’s it. The chat prefix is auto-synthesized from your server name and color. Every chat broadcast is stamped with it, and ` Need a custom prefix layout? Set `chat.prefix:` explicitly and it overrides the auto-brand.<\/p>\n —<\/p>\n ## Animated boss bars<\/p>\n “`yaml Drain the bar to zero over 10 seconds. Or `progress: { from: 0.0, to: 1.0 }` for a fill. Static bars \u2014 just a number.<\/p>\n —<\/p>\n ## Commands<\/p>\n | Command | Permission | Purpose | **Ad-hoc broadcasts** \u2014 a single unquoted word looks up a preset; multi-word or `”quoted”` arguments render as MiniMessage text. `\/bc chat “ —<\/p>\n ## Permissions<\/p>\n Three nodes. All default to `op`.<\/p>\n | Node | Grants | —<\/p>\n ## Placeholders<\/p>\n Usable in any preset text, per-recipient at render time:<\/p>\n | Tag | Value |
\n| — | — |
\n| `on-join: true` | Once per player when they connect |
\n| `every: 5m` | Every 5 minutes server-wide |
\n| `daily-at: “09:00″` | Once a day at 09:00 UTC |
\n| `daily-at: “09:00 local”` | Once a day in the server’s system timezone |
\n| `daily-at: “09:00 America\/Los_Angeles”` | Once a day in any IANA timezone |
\n| *(none)* | Manual only \u2014 fires via `\/bc scene
\nvip-event:
\n every: 10m
\n min-players: 5
\n max-players: 80
\n worlds: [survival, minigames] # Paper\/Spigot only
\n servers: [lobby] # Velocity only (backend filter)
\n permission: broadcastplusplus.vip
\n steps:
\n – { at: 0s, chat: vip-tip }
\n“`<\/p>\n
\n– **`cycle: true`** \u2014 one step fires per trigger tick, round-robin. Use with `every:` for classic tip rotations.
\n– **`cycle: true` + `random: true`** \u2014 shuffled rotation instead of round-robin.<\/p>\n
\nserver-name: “YourServer”
\nserver-color: [“#00C8FF”, “#5C78FF”] # gradient \u2014 two colors
\n# server-color: “#FFAA00” # solid \u2014 one color
\n# server-color: “red” # named color \u2014 works too
\n“`<\/p>\n
\nbossbars:
\n presets:
\n countdown:
\n text: “
\n color: RED
\n overlay: PROGRESS
\n progress: { from: 1.0, to: 0.0 }
\n duration: 10s
\n“`<\/p>\n
\n| — | — | — |
\n| `\/bc chat
\n| `\/bc title
\n| `\/bc actionbar
\n| `\/bc bossbar
\n| `\/bc scene
\n| `\/bc to
\n| `\/bc preview
\n| `\/bc list [type]` | `send` | List every preset, optionally filtered by channel |
\n| `\/bc validate` | `admin` | Dry-run the config without applying it |
\n| `\/bc reload` | `admin` | Reload config.yml (rejects on errors, keeps old live) |
\n| `\/bc studio` (alias `gui`) | `studio` | Open the in-game Studio GUI |<\/p>\n
\n| — | — |
\n| `broadcastplusplus.send` | All `\/bc` broadcasts + preview |
\n| `broadcastplusplus.studio` | `\/bc studio` GUI access |
\n| `broadcastplusplus.admin` | Everything above + `\/bc reload` + `\/bc validate` |<\/p>\n
\n| — | — |
\n| `
\n| `
\n| `
\n| `