FrontierAnnouncements
Rotating server-wide announcements with a per-player mute.
What it does
Every interval seconds the plugin broadcasts the next message from a configured list to everyone online (padded with a blank line above and below so it stands out from chat), then advances to the next one, looping back to the top when the list ends.
Two deliberate choices: the timer skips its slot without advancing when nobody is online, so an empty server never burns through the rotation; and any player can opt out for themselves with /muteannouncements, a choice that is saved to disk and survives relogs and restarts. No dependencies, no external storage.
Requires & integrates with
- Required
- Paper 26.2+, Java 25+
- Optional
- None.
- Used by
- None.
Commands
| Command | Who | What it does |
|---|---|---|
| /announcements reload | Admin | Re-read config.yml, restart the timer and rewind to message #1 (any other or omitted argument prints usage) |
| /muteannouncements | Everyone | Toggle whether you receive announcements (player-only). Aliases: /muteann, /mutebroadcasts |
Permissions
Player features default to true, staff features to op. Every node follows frontier.<plugin>.<action>, so a LuckPerms setup is e.g. lp group default permission set frontier.shop.use true. Wildcards work: frontier.reputation.*.
| Node | Default | Grants |
|---|---|---|
| frontier.announcements.admin | op | /announcements reload |
| frontier.announcements.mute | true | /muteannouncements |
Config reference
File
plugins/FrontierAnnouncements/config.yml
To apply changes
/announcements reload
| Key | Default | What it controls |
|---|---|---|
| enabled | true | Master switch. false = the timer is never started |
| interval | 420 | Seconds between announcements (420 = 7 minutes). The first message goes out one full interval after boot or reload, not immediately |
| prefix | "&8[&6Server&8] &f" | Prepended to every broadcast; & colour codes are translated |
| messages | 19-entry example list | Sent in order, one per interval, looping. & colour codes are translated; the prefix is added automatically. Empty list = nothing is sent |
Good to know
- +Replace the shipped
messages:list before going live — the defaults advertise the rest of the Frontier suite and a placeholderexample.com/…website; they show the intended tone, not text you want broadcast verbatim. - +Per-player mutes live in
plugins/FrontierAnnouncements/muted.yml(amuted:list of UUIDs). Deleting the file un-mutes everyone. - +Messages use legacy
&colour codes, not MiniMessage —<gold>style tags are sent literally.prefix:applies to broadcasts only; command replies use a fixed[Announcement]prefix. - +If nothing is broadcasting: check
enabled: true, a non-emptymessages:list, at least one player online, and remember the first message fires only after a full interval.
Looking for something specific? Search the whole suite.