Citadel Overwatch · DayZ

One Discord bot you invite. Not one you build.

Killfeed, chat relay, scheduled leaderboards, live server status and the support ticket panel — all scoped per server. No application to create in the developer portal, no token to rotate, nothing to host.

$9 / mo · the console stays free · cancel anytime

What it does

Everything is configured per server in the console, so a community running several servers never ends up with one merged feed it cannot read.

Killfeed

Live

Kills posted to a channel you choose, per server. Three servers get three killfeeds — not one channel carrying all of them with no way to tell where a kill happened.

Chat relay

Live

Messages typed in a Discord channel you choose are relayed into in-game chat as (Discord) Name: message, so staff can talk to players without logging in.

Leaderboards

Scheduled

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

Server status

Live

A live panel showing population and server state, updated in place — the bot finds its own previous message and edits it rather than reposting.

Ticket panel

Support

Players open a ticket from a panel in your Discord and get a private thread. Staff answer there or from the console — both sides see the same conversation.

Per-guild roles

Safety

Admin and moderator roles are set per Discord and never shared. A moderator in one community has no authority in another — the single most important property of a bot serving many communities.

// setup

Connected in about two minutes.

01

Invite the bot

One click. You need Manage Server on the Discord you are adding it to. There is no application to create in the developer portal and no token to generate.

02

Run /connect

The bot replies privately with a code. Both halves are required on purpose: a Discord server id is public, so a console-only flow would let anyone attach your Discord to their organization.

03

Enter the code in the console

Signed in to the organization it belongs to. The code works once and expires in fifteen minutes.

04

Point the channels at your servers

Killfeed, chat relay, leaderboards and status are configured per server under Discord in the console.

// faq

Fair questions.

Do I have to create a Discord application or host anything?
No. Citadel Overwatch is one hosted bot serving every community on Citadel — you invite it, you do not create an application, generate a token, or run a process anywhere. It also means you get fixes the day they ship instead of when you redeploy.
Why does the bot ask for Manage Threads?
Tickets run on private threads, and a private thread is invisible to anyone who is not in it — including your staff. Without that permission the ticket system appears to work and then nobody can read the tickets. It does not let the bot read your other channels.
Can I get a bot with my own name and avatar?
No. Discord has no API for creating applications, so a per-customer bot would mean somebody clicking through the developer portal for every community. Overwatch is one shared application by design.
Does the chat relay show in-game chat in Discord?
No — the relay runs Discord to game. In-game chat reaching Discord is the chat feed, fed by the mod. Pointing the relay at one of those channels does nothing, deliberately, because relaying game chat back into the game would loop forever.
What does it cost?
Citadel Overwatch is $9 a month, or $20 a month bundled with perk fulfilment. The Citadel Ops console and your support queue are free for every server you connect, whether or not you take the bot.
Does it work with more than one server?
Yes. Channels, leaderboard schedules and status panels are all configured per server, so a community running three servers gets three of each rather than one merged feed.

Your staff already live in Discord.

Give them the killfeed, the leaderboards and the ticket queue where they already are — without standing up a bot to do it.

No credit card required