Run a manual check-in
Open TiaraBot check-in at a server-chosen time and handle its result.
Create a manual check-in
The server-level monitor_channel feature applies only to automatic check-in. It does not change
manual check-in destinations, summaries, buttons, DMs, or announcements.
Use /checkin manual when a manual trigger is required. Inputs are optional:
channel_name: Target a configured running room by logical name. Otherwise, use the current room context.hour: Resolve a specific schedule hour.server_id: Target another installed event server.template: Select a supported check-in template.
TiaraBot then:
- reads expected fills from the sheet.
- posts the filler-facing Check in button in the running room’s configured check-in channel.
- returns the moni summary through the invoking mana/moni’s command response.
- sends configured filler check-in DMs and moni DM notifications.
- posts a tentative room order in the running channel when enough fills are available.
Moni summary returned by the command
The command response is an ephemeral embed. It confirms delivery and reports empty slots plus the players moving out, staying, and moving in for the selected hour. Fillers with linked accounts are shown as mentions, but the response does not ping the assigned moni or include the automatic check-in line. Manual check-in does not post a second summary in the running channel.
Check-in prompt posted for fillers
This is a separate public message in the running room’s configured check-in channel. The canonical filler instructions are on Check in for your fill shift. The complete prompt appears immediately so its mentions notify fillers. It may briefly include the muted line Controls are being prepared... while TiaraBot registers the message, then updates in place with the Check in button.
Tentative room order posted by check-in
When enough fills are available, check-in also creates this separate public message in the running channel. The order appears immediately and may briefly include the muted line Controls are being prepared... before its controls appear. It is not part of the ephemeral command response.
Monitor: Moni
P1: Bloom Team | Tierer
P2: Theerie the Miku Enjoyer | Full Fill (+232%, enc)
P3: Wonderlands | Full Fill (+224%)
P4: Vivid BAD SQUAD | Full Fill (+218%, not enc)
P5: Leo/need | Heal (+180%)
In: Theerie the Miku Enjoyer
Out: AiriFan39Automatic check-in is a separate flow
Automatic check-in runs at minute 45, posts the monitor summary and any required handoff in the configured mana/moni channel, and automatically prepares an eligible tentative room order without a mana/moni command invocation. Without a configured monitor channel, its summary retains the legacy running-room destination.
Keep auto check-in disabled when the server uses /checkin manual for its own timing so the same hour is not opened by both paths.
Direct-message notifications
Fillers who enabled check-in DMs receive this reminder:
The assigned moni receives a separate notification when monitor DMs are enabled:
Handle the result
When a filler presses the button, TiaraBot privately confirms the interaction:
It then records the filler, reapplies the running channel's lockdown role when one is configured, and updates the original check-in message:
Finally, a successful first check-in creates a new announcement in the running channel:
Use the checked-in state plus /schedule list and /slot list to identify scheduled, overfill, or standby options.
The next escalation is server-specific: standby-first and direct-to-emergency are both valid local procedures. TiaraBot does not send that ping or assign the replacement.
Use /preference monitor-dm status|enable|disable to control your monitor notification. It does not change the schedule or check-in timing.