Discord bot
One bot serves every community, and it holds no credentials of its own. Each slash command runs as the Discord user who typed it, so Aquilon's permissions, tenancy and audit trail apply unchanged: a Discord admin without the Aquilon role gets a polite refusal, and everything anyone does lands in the audit log with their name.
Pairing
- In Aquilon: Settings → Integrations → Generate pairing code.
- In Discord:
/aquilon pair code:XXXXXXXXwithin 15 minutes, by a member with org management rights. /aquilon channels server:<name> status:#channel alerts:#channelto route the status card and the alerts.
A Discord server belongs to one organisation; an organisation may pair several Discord servers.
Commands
| Command | Needs | Does |
|---|---|---|
/roster |
view players | who is on, by team and squad |
/server |
view players | live status: players, queue, layer, factions |
/player |
view players | search the community's player base |
/bans |
view bans | recent active bans |
/admin-calls |
view players | open admin calls and reports |
/warn, /kick |
act on players | in-game moderation |
/ban |
manage bans | a ban row, enforced on every server |
/broadcast |
act on players | server-wide message |
/next-layer |
control servers | set the next layer |
/aquilon status, /aquilon-ping |
member | what this Discord is connected to, your role |
Every command takes an optional server:; with one server it is implied.
In the background
- A status card per server, edited in place every 30 seconds: players and cap, queue, layer, clock, factions.
- Alerts within 15 seconds: admin calls from
!adminin game, teamkill reports, watchlist and Community Ban List joins, posted to the server's alerts channel.
Webhooks
Independent of the bot, signed webhooks post the events you pick — bans, kicks, teamkills, seeding milestones, crashes — to any channel, with a shared secret so your side can verify them.