---
title: Discord bot commands (staff)
description: Staff-only commands for server setup, announcements and player moderation.
---

The **Athena** bot on your event's Discord server has three staff commands: one for setting the server up, one for announcements, and one for looking up and moderating players.

The commands available to every member (`/help`, `/rules`, `/leaderboard`, `/me`, `/team`, `/challenges`, `/announcements`, `/stats`, `/faq` and `/link`) are documented in the [Player Guide](/players).

## Before you start

1. **Connect the server.** Open the event's **Discord** page in the admin panel and press **Connect Discord server**. One Discord server belongs to one event.
2. **Pick the staff role.** The same page lists your server's roles; choose the one your organizers hold. Staff means exactly that role, and **until you pick one, every staff command refuses**, including for you. Change it from the same card whenever you like.
3. **Give the bot its permissions.** It needs Manage Roles, Manage Channels and Manage Webhooks. A missing permission fails the whole `/setup` run; no step is silently skipped. Grant them before you start.

The staff role is only ever chosen in the admin panel; the bot does not create it and does not read Discord's own permissions.

## /setup

Run it in the channel you want to configure; the channel is not something you pass as an option. Every option is safe to re-run: the bot edits its existing post in place, so you never get a second copy.

| Option | What it does |
|---|---|
| *(none)* | Hides every channel from members who have not linked their account, leaving only the verify channel visible. Run this after you have set the verify channel. |
| **Verify channel** | Posts the linking panel and makes the channel visible to everyone. |
| **Rules channel** | Posts your event's rules, taken from the event settings, and locks the channel to verified members. |
| **Tickets channel** | Posts the **Open a ticket** panel. |
| **Welcome channel** | Turns the channel into a join feed. The bot posts a notice as each member joins. |
| **Leaderboard channel** | Posts a standings message the bot keeps up to date. |
| **Announcement feed** | Creates a webhook so every announcement you publish on the event site is posted here. |
| **First blood feed** | Creates a webhook so first bloods are posted here. |

The first time you run `/setup`, the bot creates a **Verified** role if one does not already exist. That is the role the linking flow grants, and the one your locked channels open for.

:::note[Set the verify channel first]
Run `/setup` with **Verify channel** before the bare `/setup`. The bare run hides every channel except the verify channel, so with no verify channel recorded it hides everything.
:::

## /announce

Posts your message to the announcement feed channel **and** publishes it as an announcement on the event site, so both audiences see the same thing.

- **message** (required): the announcement text, up to 2,000 characters. Basic Markdown is carried through to the site.
- **title** (optional): defaults to *Announcement*.

If no announcement feed is set up, the message is still published on the site and the bot tells you which option to run.

## /player

| Subcommand | What it does |
|---|---|
| `info` | Rank, points, solves, team, whether their Discord is linked, and whether they are banned. |
| `ban` | Bans the player on the platform, ends their sessions immediately, and bans them from the Discord server. Takes an optional reason. |
| `unban` | Lifts both the platform ban and the server ban. |

All three take a platform **username**.

:::note[Ban from the panel when the player needs telling]
A ban from Discord does not send the account-suspended email. Use the panel's player page when you want the player emailed.
:::

## What the bot does on its own

With an **Announcement feed** channel set, the bot posts when the event starts, when the scoreboard freezes and when it ends. With a **Leaderboard channel** set, it keeps that standings message current. Neither happens until the matching channel is configured.

When the event ends and its resources are torn down, the bot leaves the server. Your channels and history stay as they are, including the permission overwrites `/setup` applied and the "Athena" webhooks it created, so unlock any channels you want open afterwards.
