Reference

Configuration commands

A configured Bot Manager runs these commands unless a row says otherwise. Results are private.

/config status

Show setup readiness, Bot Manager roles, participant command visibility, cleanup deadlines and runtime health. A server administrator with Manage Server can also run it.

/config announcement channel:<channel>

Save the channel for automatic draw, motion and veto posts.

/config meeting link:<HTTPS URL>

Save one Zoom or Google Meet link for the tournament. It appears in linking confirmation DMs, private /room replies and draw DMs.

/config language mode:<vi|en>

Set the bot’s language. The default is English. See Language.

/config institution enabled:true

Create and maintain one Discord role for each CalicoTab institution. Leave this disabled if your server does not need institution grouping.

/config timezone zone:<IANA timezone>

Set the timezone for staff-entered times. Use zone:api to return to CalicoTab’s timezone. See Schedule & round timing.

/config veto enabled:true duration:<minutes>

Enable motion veto and set its duration (1–15 minutes, default 5). Requires Manage Server. See Veto.

/config command-log mode:<on|off>

Enable or disable the private Command Log. It defaults to on. It records successful Bot Manager commands plus meaningful automation transitions. Existing messages and unresolved deliveries remain when logging is off. The log never includes raw options, tokens, Private URLs, meeting links, or DM content.

Language

/config language mode:<vi|en> sets the language for:

• public announcement cards, participant DMs and invitation emails;
• the connect button, private form, unlinked instructions and welcome-back DMs;
• Private URL delivery replies, check-in confirmations and linking errors;
• veto forms and results, delivery previews and summaries, and actionable Bot Manager alerts.

In Vietnamese, the connect button reads Liên kết tài khoản, and bot text uses tin nhắn riêng for DM. Command names and participant or staff content stay unchanged.

• Invitations: changing the language after a preview needs a new preview. Queued emails keep their original language.
• Onboarding message: repost /onboard to update its visible text.

Bot permissions

The bot never requests Administrator. It requests these permissions:

Permission	Used for
Manage Channels	Creating its private Command Log.
Create Instant Invite	Participant invitation joins.
Manage Roles	Assigning tournament roles.
Manage Nicknames	Nickname synchronization.

For a server that already has the bot, a server administrator must grant missing permissions. The Developer Portal permission calculator does not grant them. In the announcement channel, the bot also needs to view and send messages, embed links and mention everyone.

Staff roles and CAP

• Bot Manager roles: Tab and CAP are the default Bot Manager roles for running staff commands.
• Automatic CAP: the bot assigns CAP to linked Core Adjudicators.
• Keeping CAP: linking as an Adjudicator or refreshing roles keeps an existing CAP role and its nickname prefix. This applies even if the Core Adjudicator checkbox is not selected.
• Revoking CAP: clear the Core Adjudicator checkbox in CalicoTab and remove the Discord role manually.

Invitation status

/invite status shows these counts. They overlap: a participant who confirmed appears under both SMTP accepted and Claimed.

Status	Meaning
Queued	Waiting to be sent.
Sending	Being sent now.
SMTP accepted	The mail server accepted it. This does not prove it reached the inbox.
Failed	Not sent: the mail server rejected it, or setup changed, the participant was already linked, or the invitation expired or was revoked while queued. Check the address and setup in CalicoTab, then resend.
Delivery unknown	The result is uncertain. It is never retried automatically; confirm with the participant before resending.
Claimed	The participant confirmed and is linked.
Expired	Seven days passed without a confirmation. Resend.
Revoked	Cancelled with /invite revoke, or replaced by a resend.

Runtime health

/config status includes a private Runtime health — this server panel. A server administrator with Manage Server or a configured Bot Manager can check it.

• Shows: the last successful CalicoTab poll, failures or backoff, running background work, this server’s managed Discord queue pressure, and this server’s check-in queue.
• Check-in queue: running and waiting check-in clicks, the oldest wait, and results since the time shown (about the last 15 minutes, or since the last restart). Confirmed means CalicoTab showed the requested state and any change was recorded by the bot. Not saved and requests that never started (wait expired, window closed or changed, queue full or duplicate) changed nothing. Counts reset on restart, so requests cancelled by a restart are not shown. Result uncertain means a CalicoTab write was attempted but not confirmed: check the participant in CalicoTab before asking them to click again.
• Does not: start a poll, retry messages or check-ins, or reset inactivity.
• Stale: no successful poll for over two minutes.
• Taking longer than expected: a warning about a long-running job, not a confirmed failure.
• Large participant DM batches: delivery can take several minutes while progressing normally. The participant stall warning requires two minutes without progress.
• Limits: poll history resets after a restart, and a successful poll does not confirm message delivery. Queue counts exclude sends outside the managed queue. Missing runtime data is shown as unavailable.

Wait through active work or backoff, avoid repeating message-sending commands, and check again in a minute. If delays persist, contact Support. For authentication failures, follow Change tournament credentials if needed.

Bot Manager alerts

• DM alerts: the server owner and configured Bot Managers receive DMs for CalicoTab access problems and missing announcement permissions.
• Cooldown: repeated changes are summarized after a ten-minute manager cooldown. New credential or permission problems can alert immediately.
• Command Log: circuit-breaker details, scheduler updates and recoveries go to the private Command Log. Enable it with /config command-log mode:on.
• Recovery: recovery requires at least two minutes of stability. Use /config status for current health.

Automatic cleanup and retention

Two cleanup timers run at the same time. The bot leaves when either timer ends first.

• After 40 days without activity: the server owner and configured Bot Managers receive one warning DM.
• After 45 days without activity: the bot deletes the server’s saved data and leaves.
• 85 days after setup: the server owner and configured Bot Managers receive one warning DM.
• 90 days after setup: the bot deletes the server’s saved data and leaves. Run /setup bot again before then to restart this period.

Recorded activity means a successful participant command, an active check-in button, or an authorized Bot Manager command. Automatic CalicoTab checks, rejected requests, and /config status do not reset inactivity.

Run /config status to see both deadlines and the date that comes first. To reset inactivity, use a normal bot command or an active check-in button. If one person cannot receive DMs, the bot still warns everyone else who can receive them.

To delete data now, remove the bot. See the Privacy Policy for retention.