The whole thing at a glance

Overview

What is running, what has been counted, and what changed.

Not confirmed at build time

Everything this bot does, in one place.

One page for what is running, one for every system it gates, one for every command it publishes, and one for the host it runs on. Nothing here is a mock-up: the systems and commands below are read out of the registry the bot itself boots from, so a feature that is added or retired moves this hub with it.

— servers — members reached 12 systems 90 commands
Open the console Browse the systems Add it to a server

The live read

gateway

This page asks the bot's own host for one small public reading — counts, no names — and keeps asking every thirty seconds while the tab is open. If the host is asleep, the figures stay as built and the page says so instead of showing you a zero.

read just now

What it has counted

live
— messages, last 7 days — people seen, last 7 days
Every window

Where it stands

1 reading wants attention

Each line is a question the deployment can already answer about itself. Nothing here is a guess and nothing here is a to-do list: a green line means the reading came back clean, and an amber one names what would turn it green. A line that cannot be read from here says so, and the live read fills it in.

The gateway The bot is not connected to Discord as of this page's reading. A free host sleeps when nobody knocks, so this is usually the first reading after a wake rather than an outage.
The console
Configuration This page was built somewhere other than the deployment, so it asks the host itself for how many settings are missing.
Read live
The public site's own check No verdict recorded in this process. A fresh process has not run the check yet.
The console
The feature registry All 12 systems validate: no duplicate ids, no command claimed twice, no gate naming a system that does not exist.
The systems
Reliability Nothing has been read from the watcher in this process yet.
The readings

At a glance

12 systems, 11 of them switchable

A system is a feature an administrator can turn on or off per server. The 1 that are not switchable are the core utilities — they stay reachable everywhere, by design.

All of them, in detail
Progression 1 system
Leveling & XP
Economy 2 systems
Economy & Casino Market
Management 1 system
Moderation & Logs
Security 1 system
Automod & Shield
Community 3 systems
Starboard Social Roleplay Activity Tracker
Support 1 system
Support Tickets
Entertainment 1 system
Fun & Memes
Games 1 system
Mini-Games Hub
Core 1 system
System & Server Control

What changed

The last few things that moved

Read straight out of the project's own changelog, newest first — the same file the team writes for itself, not a summary written for a page.

The whole history
The console said "Unknown server" because the gateway cache it read is empty for the first minute after every restart, and the badge said "Live" through a reconnect because it was reading a flag that never clears — and the lag turned out not to be the server at all
Unreleased
The landing page is three pages now — a front door, /systems and /start — sharing one layout, and the front door is down from a 68 KB scroll that answered everything to a 22 KB page that answers one question
Unreleased
The product has four themes now instead of one indigo, and the control that picks one costs no flash of the wrong colour on any of the eight pages
Unreleased
There is one answer now to how many systems and how many commands — twelve and ninety, on every surface — the footer stops linking a locked door, and the landing page stops publishing the operator's own laptop as the deployment
Unreleased