📢 Broadcast system — every detail
The composer
Hub → Events → Broadcast. A message goes to every online player; how it looks follows the notification toggle (mod UI or the ZYAD toast). Every send is validated server-side.
| Control | Behaviour |
|---|---|
| Text | Free text, may contain the {t} placeholder (see countdown). |
| Style | Info / Warning / Event — sets the message heading. |
| Mode | Click through: Once (immediately) · Countdown (N messages on an interval, {t} = time left, e.g. “Restart in {t}”) · Repeat (same message N times). |
| Count / interval | For countdown/repeat; capped at 1–20 messages and 5–3600 s. |
| Send | First message goes out immediately, the rest is scheduled server-side. |
Templates
Reusable messages (name / text / style), stored in Broadcast/broadcasts.json.
Sensible defaults are created on the first server start (restart / event / rules / Discord).
| Control | Behaviour |
|---|---|
| Use | Loads the template into the composer, where you can still adjust it before sending. |
| X | Deletes the row. |
| Save | Saves the whole list; the server sanitises it (trims, clamps, drops empty rows). |
Rotation (automatic sending)
| Control | Behaviour |
|---|---|
| Master switch | Rotation on/off (default: off). |
| Template | Click-through button cycling all templates. |
| Mode | Interval (minutes) ↔ time of day (HH:MM, local server time). |
| Server time | Shown live in the editor — no guessing time zones. |
| Active / X | Toggle or delete each row individually. |
| Save | Takes effect live — the scheduler re-arms immediately. |
Scheduler details
- Interval entries fire for the first time one interval after boot/save — no message spam at server start.
{t}is stripped in interval mode. - Time of day without
{t}: exactly one message at that time. - Time of day with
{t}: automatic advance warnings 30/15/10/5/2/1 minutes before, with{t}= time left (“5 min”). No zero message — the last warning is at 1 minute. - Timing is accurate to the second, each moment fires at most once per day (reset at midnight), moments already past at boot are skipped, and a ~2 minute catch-up window covers restarts that land right on one.
The restart trick: a single time-of-day entry with a
{t} template
(“Server restart in {t}!”) replaces six manual announcements — the whole warning ladder runs
by itself.Design tips
- Put rules and Discord reminders on long intervals (45–90 min) — rotating messages lose their value once they become wallpaper.
- Use the styles consistently (Info = neutral, Warning = action needed, Event = get over there!) — players learn to read the heading and colour at a glance.