Why Ani looks smaller than it used to
Short version: the bot got a lot of updates in a short time, a few things broke along the way, and instead of keeping broken commands online the team pulled them back until they're stable. This page is a straight answer to "where did everything go."
What actually happened
Ani went through a lot of changes at once — new dashboard system, a rebuilt API, and a pile of new commands landing on top of the existing ones. That kind of churn has a cost, and the cost showed up as bugs across the board: search commands failing, list commands dropping entries, some things just not responding at all.
Rather than leave broken commands up and ask people to guess which ones worked, the decision was to take them offline. Fewer commands that actually work beats a long list that mostly doesn't.
What's live right now
On the bot itself: /news, /info, /stats, /setprefix, /purge, /afk set, and /afk list. A couple of the prefix forms of those — ?afk, ?info, ?stats, ?purge — are still around for muscle memory.
On the dashboard: welcome, goodbye and boost messages — including the image-card editor — plus which channels subscribe to which news sources. That part is fully built out and isn't going anywhere.
For the exhaustive list, the Commands page is kept accurate. If you want the bot's own word on it, type /info in Discord.
What's coming back
Anime and manga search, the schedule commands, theme music playback, the AniTrack list system, and the fuller moderation set — /kick, /ban, /unban, and richer purge filters. None of that is gone for good. It's on the bench while it gets fixed, tested, and made stable enough to trust again.
They'll come back one at a time. Not all at once, and not on a fixed schedule — whenever each piece is actually ready. The Updates page is where that shows up, and this page will keep pointing to whatever's currently true rather than what's eventually planned.
Why the site and the bot can still drift
The Commands page reflects what's shipped. This page explains the reasoning. Neither is a live readout of the bot's process at any given second — if a command is mid-redeploy or temporarily paused while something else gets built, the site won't always know within the same minute.
So if something on here doesn't line up with what you see in your server, that's expected. The bot's own /info is always going to be the closest thing to ground truth.
Reporting something
If a command that's supposed to be live doesn't respond, or a welcome message doesn't fire, or the dashboard saves the wrong thing — that's a real bug and worth flagging. Bring it to the support server or use the report page.
If a command that's on the "coming back" list doesn't respond, that's not a bug — it just hasn't come back yet.