Citadel Overwatch

One bot, serving every community on Citadel. You invite it; you do not create a Discord application, generate a token, or host anything.

That is a deliberate trade. A bot per customer is not possible in any case — Discord has no API for creating applications, so somebody would have to click through the developer portal for every server — but even setting that aside, one hosted bot means you get fixes the day they ship instead of when you redeploy.

Connecting

1. Add Citadel Overwatch to your Discord — you need Manage Server on the Discord you are adding it to
2. Run /connect. Same permission, and it is how Citadel knows the server is yours
3. The bot replies privately with a code. Enter it in the console, signed in to the organization it belongs to

The same link is on the Discord screen in the console, next to the box you paste the code into.

What it asks for, and why

Discord will show a permission list. It is short on purpose:

| Permission | What it is for | | --- | --- | | Read and send messages, embed links | Posting the killfeed, chat relay and status | | Read message history | Finding its own previous message to update instead of reposting | | Create and manage private threads | Some Discord surfaces create private threads; without this they appear to work and then nobody can read them |

Manage threads is the one worth understanding before you decide. It does not let the bot read your other channels.

Both halves are required, and the reason is worth knowing: a Discord server id is public. A console-only flow would let anyone attach your Discord to their organization, and hand their members control of your game servers.

The code works once and expires in fifteen minutes. Treat it like a password — anyone holding it can attach your server to their organization.

What it does

Killfeed — kills posted to a channel you choose, per server.

Chat relay — messages typed in a channel you choose are relayed into in-game chat as (Discord) Name: message.

This goes Discord → game. It is not where in-game chat appears; that is the killfeed and chat feed, fed by the mod. Pointing the relay at one of those channels does nothing, deliberately — relaying game chat back into the game would loop forever.

Leaderboards — posted automatically on a schedule you set per server. Hourly on a quiet server reads as spam; daily on a busy one is stale before anyone sees it, so the cadence is yours.

Server status is a live panel showing population and state. A server that has never reported says waiting, not offline. Offline means it used to report and the game box is down. A player lookup (/statistics) on a waiting server says waiting, not that they have never been seen.

There is no ticket panel. /ticket-panel was retired. See Getting help.

Channels are per server

A community running three servers gets three killfeeds and three chat relays, not one channel carrying all of them with no way to tell which server a kill happened on. Set them per server in the console, under Discord.

Roles

Set your admin and moderator roles in the console. With none configured, the bot falls back to Discord's own Manage Server and Kick Members permissions.

Roles are per guild and never shared. A moderator in one community has no authority in another, which sounds obvious and is the single most important property of a bot that serves many communities at once.