TMDevelopmentTinulica & Maiky

Announcements

Announcements: automatic messages in order or random, per permission and per world

In announcements.yml:

settings:
  interval-seconds: 180   # seconds between two automatic announcements (min. 5)
  random: false           # false = in order, true = random (never the same twice in a row)
  min-players: 1          # no automatic announcement with fewer players online (0 = always)

announcements:
  store:
    bossbar:
      text: "&7Support the server: <gradient:#BB6BD9:#56CCF2><bold>store.your-server.com</bold></gradient>"
      color: PURPLE
      style: PROGRESS
      seconds: 15
      countdown: true

The name under announcements: is its id (no spaces). Every announcement uses the message format: chat, title, action bar, boss bar, sound and commands, in any combination.

Option
enabled: falseturns it off without deleting it
in-rotation: falsenever sent automatically, only with /fmes announce <id> (events, restarts...)
permission: """" = everyone, otherwise only players with this permission see it (e.g. group.default to hide it from staff / VIPs)
worlds: [][] = all worlds, otherwise only players in these worlds, e.g. ["world", "world_nether"]
min-players: 0(1.0.4+) the rotation sends it only with at least this many players online (0 = no limit)
max-players: 0(1.0.4+) ... and only with at most this many (0 = no limit)
at: [](1.1.0+) fixed times of the day, e.g. ["12:00", "21:00"] (see below)
days: [](1.1.0+) with at: the days of the week ([] = every day)
holiday: ""(1.1.0+) only while that holiday is active
  • (1.0.2+) An automatic announcement that nobody online can see (its permission or worlds) doesn't waste the turn: the next one is sent instead.
  • Placeholders are filled for every player: "Hi {player}" shows each one his own name.
  • With chat: face: true every player sees his own face.
  • The default file has five examples: discord (chat), vote (chat + action bar), store (boss bar), tips (chat) and event (title + chat + sound, only by hand).

At fixed times (1.1.0+)

An announcement can be sent at fixed times of the day, e.g. the PvP night every Friday and Saturday at 21:00:

announcements:
  pvp-night:
    at: ["21:00"]
    days: [FRIDAY, SATURDAY]
    title:
      title: "<gradient:#EB5757:#F2994A><bold>PVP NIGHT</bold></gradient>"
      subtitle: "&7Starting now at &f/warp pvp"
    sound: "entity.ender_dragon.growl"
  • Times are 24 hours ("9:00", "21:30"), in the timezone of config.yml (empty = the server's time zone). Quotes are best, but at: [21:00] works too.
  • days: MONDAY ... SUNDAY, or short MON ... SUN. [] or missing = every day.
  • With at it is only sent at those times, never in the normal rotation. Add in-rotation: true to have both.
  • permission, worlds, min-players / max-players, settings.min-players and holiday still count; nobody who can see it = not sent.
  • It doesn't move the timer of the rotation. A restart or reload at 21:00:30 never sends the 21:00 one twice.
  • Need it several times a day? at: ["10:00", "14:00", "18:00", "22:00"].
  • /fmes list shows the times next to the name, e.g. (at 21:00).
  • Wrong times or days are written in the console at start and skipped.

Announcements by player count (1.0.4+)

Each announcement can have its own min-players / max-players. Example: ask to invite friends only when the server is quiet, and announce the PvP event only when there are enough players:

announcements:
  invite:
    chat:
      lines:
        - ""
        - "<center>&7Only &f{online} &7players online..."
        - "<center>&7Invite your friends, more players = more fun!"
        - ""
    max-players: 10      # only with 10 players or fewer
  pvp-event:
    title:
      title: "<gradient:#2F80ED:#56CCF2><bold>PVP EVENT</bold></gradient>"
      subtitle: "&7Join now with &f/warp pvp"
    min-players: 20      # only with 20 players or more
  • With 15 players online neither of them is sent: the rotation goes to the next announcement, no turn is wasted.
  • settings.min-players still counts for every announcement.
  • /fmes announce <id> ignores them: by hand you can always send it. /fmes announce next respects them; only when no announcement can be sent right now it sends the next one of the list anyway.

Commands: /fmes list, /fmes preview <id>, /fmes announce <id>, /fmes announce next.

(1.0.3+) /fmes announce next sends the same announcement the automatic rotation would send now (skipping the ones nobody online can see), then the timer starts again from zero. Example with interval-seconds: 180: you run /fmes announce next at 10:00, the next automatic one comes at 10:03, never a few seconds after yours. /fmes announce <id> doesn't touch the timer.

Last updated

Sign in

New here? Just enter your email: the account is created when you click the link. No password needed.

or

We send you a link that signs you in with one click. It works for new and existing accounts.

Sign in with a password instead

By continuing you accept the Terms & Conditions and the Privacy policy.

Staff: open “Sign in with a password instead” and type your username instead of the email. After the password we ask for your 2FA code.