# How to tell a Discord bot has been abandoned

> The observable signals that a Discord bot is no longer maintained, and how to check them before you build a server around it.

- Canonical: https://discordbots.blog/blog/signs-a-discord-bot-is-abandoned
- Published: 2026-10-05
- Author: The Field Guide desk
- Competitor facts checked: 2026-09-01
- Sources:
  - Discord App Directory (https://discord.com/application-directory) — checked 2026-09-01
  - Discord — App Directory announcement (https://discord.com/blog/app-directory-is-here-mods-and-admins) — checked 2026-09-01
  - Discord developer docs — Gateway (https://docs.discord.com/developers/events/gateway) — checked 2026-09-01
- Publication: The Field Guide, an independent site not affiliated with Discord Inc.

---
Bots seldom announce their retirement. They go quiet, keep running, and slowly stop matching the
platform around them. These are the checks that surface it in about ten minutes.

## Check the changelog first

A dated changelog or release feed is the single most informative artefact a vendor publishes. What
you are looking for is not frequency but *recency and substance*: entries within the last few
months describing actual changes, rather than a year-old entry followed by silence.

Absence of a changelog is not itself damning — plenty of maintained bots never kept one — but its
presence and abrupt stop is a strong signal.

## Look for platform-feature adoption

This check is the hardest of the five to fake, because adoption requires active work. Discord ships new capabilities
regularly, and adopting them requires someone to do work. A bot that still has no slash commands,
does not use Discord's newer component types, or has no support for forum channels is telling you
when its development effectively stopped.

Check the bot's own command list in your server: if everything is a prefix command and nothing
appears in the slash picker, that dates the last significant work fairly precisely.

## Read the support server, not the marketing

Spend ten minutes in the vendor's support server and read the last week rather than the pinned
messages. Two patterns matter:

- **Bug reports scrolling past unacknowledged.** Not unresolved — unacknowledged. A maintained
  project replies even when it cannot fix.
- **Members answering members while staff never appear.** A community can keep a support server
  feeling alive long after the developers have left. It is a genuinely good sign about the
  community and tells you nothing good about the product.

## Documentation that no longer matches

Open the docs and try one thing. If the documented command does not exist, or exists with different
options, the documentation and the code have diverged — which means nobody is updating both, which
usually means nobody is updating either.

## What is *not* a signal

**Uptime.** A bot can run untouched for years. Being online means the host is paid, not that anyone
is home.

**Server count.** Installations accumulate and rarely get cleaned up. A large number reflects
history, not current health.

**Age.** Long-lived bots are often the best maintained. What matters is whether maintenance is
ongoing, not when it started.

## What to do about it

An abandoned bot doing something simple and self-contained — a reaction-role panel, a static
welcome message — can reasonably be left alone; it will keep working until Discord breaks it.

An abandoned bot holding data you care about, or holding broad permissions, is different. Data with
no maintainer has no recovery path, and permissions with no maintainer have no security response if
the bot's token is ever compromised. Those are the ones to migrate off deliberately rather than
when forced.