Configure an event server

Inspect before changing

Use /server list_config and /channel list_config before a shift or after a handoff. Target another installed server only when necessary with server_id.

Event-server settings

/server supports these configuration changes:

• /server set sheet: Link the Google Sheet used for schedule-backed operations.
• /server set auto_checkin: Enable or disable TiaraBot’s minute-45 automatic check-in.
• /server set monitor_channel: Send automatic monitor summaries and handoff check-ins to one shared mana/moni channel.
• /server unset monitor_channel: Restore the legacy running-room destination for automatic monitor summaries.
• /server add monitor_role and /server remove monitor_role: Control recognized moni roles.

It is not a general event-profile command.

Optional mana/moni channel

Use /server set monitor_channel channel:#mana-moni to give automatic check-in a shared monitor destination. /server list_config shows the current value. The channel may be private, but TiaraBot must be able to view it, send messages, embed links, and use application-command components there. Use /server unset monitor_channel to remove it.

The monitor channel cannot also be registered as a running room. TiaraBot rejects either configuration order: setting a running room as monitor_channel, or later setting the configured monitor channel to running:true. It may still be used as a filler-facing checkin_channel.

Running-room settings

Use /channel set on the current or selected Discord channel to configure:

• running: Whether the channel is a running/private-room coordination channel.
• name: The logical channel name used by commands such as /screenshot.
• role: An optional lockdown role TiaraBot reapplies at check-in and removes during kick cleanup.
• checkin_channel: Where the filler-facing Check in message is sent.

Use /channel unset to remove only the mistaken field, then /channel list_config to verify the result.

The /channel list_config response labels this channel-level field Lockdown role.

Optional lockdown role

The running-room lockdown role is optional. When it is configured, TiaraBot assumes the Discord channel’s permissions use that role as a visibility gate. TiaraBot grants the lockdown role at check-in and removes it from people who should no longer have room access during automatic cleanup on automatic-check-in servers or during manual kick cleanup.

This lockdown role is separate from the server-level monitor roles registered with /server add monitor_role. Monitor roles authorize mana/moni commands; the lockdown role gates visibility for one running channel.

The visibility gate can keep unrelated people from seeing the in-game room code and entering to break or grief the room. /channel set tells TiaraBot which role to manage. After setting it, use /channel lockdown_setup to apply the standard Discord permission overwrites for the running channel.

If the running room is visible without a managed role, leave role unset. TiaraBot will skip lockdown-role cleanup for that channel, and there is no need to run /kick manual.