TiaraBot update announcements
Receive occasional TiaraBot feature and service updates in an event server.
TiaraBot can post occasional product updates in a server that has opted into the
update-announcements feature flag. The feed is intended for concise release notes: it tells the
server what changed without interrupting tiering operations or requiring anyone to run a command.
One announcement per update
Each published update is delivered at most once per server. TiaraBot does not use @everyone,
@here, or role-wide mentions for this feed.
What gets posted
Announcements are short Discord embeds with a release title, a plain-language summary, and an optional link to the relevant TiaraDocs page. They may describe a new TiaraBot capability, a dashboard or access change, or a service behavior that mana/moni should know about.
The feed is independent of schedule, check-in, room-order, and team-submission messages. Turning it on does not change any of those workflows.
Where announcements go
By default, TiaraBot chooses one sendable server conversation in this order:
- Discord’s system channel, when one is available.
- A channel named
#general. - The first available text or announcement channel that TiaraBot can send to.
The #general name match is case-insensitive. A server manager can set an explicit destination
with Dashboard → Settings → Server → Update announcement channel or
/server set announcement_channel channel:#announcements. TiaraBot uses that channel for updates
while it remains available and sendable. Choose Automatic routing in the dashboard or use
/server unset announcement_channel to clear the setting. Clearing it restores the system-channel,
#general, then first-sendable-channel order above. An unset channel does not disable the feed.
The server must allow TiaraBot to view and send messages in the selected channel. If the configured channel is unavailable or TiaraBot cannot send there, TiaraBot does not silently switch to a different channel. Clear the setting or fix the channel permissions before retrying.
An update is eligible only when its publication time is strictly after the server's joined_at
timestamp.
If no suitable conversation is available under the active destination rule, the update is not delivered. It remains safe to retry after channel permissions or server configuration are corrected.
Delivery timing and history
The service records a delivery for each server and update before considering that update complete. Retrying a gateway event or restarting TiaraBot therefore does not duplicate a message.
TiaraBot only considers updates published after it joined the server. Enabling the feed later does not recreate updates from before the bot joined, and a server may receive several still-eligible updates the next time TiaraBot processes its guild membership event.
The update-announcements flag always gates delivery. A server receives no update while the flag
is disabled, even when an announcement channel is configured. Setting or clearing the channel does
not enable the feed. The TiaraBot application owner can enable or disable the flag with
/feature_flag; contact the TiaraBot maintainer when the server should be enabled or disabled.