Bot Rescue: fix a broken or outdated Discord bot

Bot Rescue is my answer to "can someone fix my Discord bot?": a fixed-price fix for one bot written with discord.js or discord.py. I find out why it is offline, silent or throwing errors, fix it, and send you a short written report of what was wrong, within 3 business days, for $149. If I can't fix it, you pay nothing.

It's meant for bots whose developer has moved on, bots that broke when Discord changed its rules, and bots stranded on a free host that shut down or on a library version that no longer installs cleanly. If you want to try yourself first, the Discord bot not working guide goes through the common causes by symptom, with tested fixes.

What a rescue covers

Anything that stops an existing bot from doing what it did before:

• Offline bots. A process that crashes on start, a host that sleeps or closed down (Heroku's free dynos began shutting down on November 28, 2022, and Glitch stopped hosting projects on July 8, 2025), a token that was reset or leaked, and crash loops that hit Discord's limit of 1,000 logins a day, which resets the token.
• Bots that are online but broken. Prefix commands that no longer read messages, "Used disallowed intents", slash commands that vanished or show up twice, "The application did not respond", Missing Permissions and rate-limit errors.
• Bots broken by recent Discord changes. The permission changes of February 23, 2026 (Pin Messages, Create Expressions and Create Events became required), the June 10, 2026 privileged intent rules, and bots that rely on seeing channels they have no access to, which Discord hides from bots starting November 16, 2026.
• Outdated setups. Code that crashes on the Node.js or Python version your host runs now, or that pulls a new major library version on every fresh install.

Upgrades and migrations

Four moves come up with broken bots: moving to a working host, updating a Discord bot to discord.js v14, moving discord.py 1.x code to 2.x, and migrating a BotGhost bot to code. The first three fit in a rescue when the bot is small enough; the last is a rebuild.

If the diagnosis shows that an upgrade is really a rewrite, for example a large v12 bot where nearly every file needs changing, I stop, tell you what I found and quote the rewrite separately. If you don't go ahead, the $149 comes back to you.

What isn't covered

• New features and new commands. Changes beyond the fix are billed at $90 an hour in prepaid 5-hour blocks, or quoted as a build.
• Rewrites. Quoted separately, as above.
• More than one bot. Each bot is its own rescue.
• Hosting fees. Your host bills you directly, unless Care covers hosting for you.
• Other languages. Bot Rescue covers discord.js and discord.py.
• Bots that break Discord's rules. I don't fix selfbots, member-inflation bots, gambling bots or anything that scrapes servers you don't own. Discord's Developer Policy bans member inflation, scraping and illegal gambling, and Discord forbids selfbots outright.

Sometimes rebuilding is cheaper

Fixing is usually cheaper than rebuilding, but not always. I'll tell you when I think a rebuild is better value, usually in one of these cases:

• The code is so old and tangled that reaching discord.js 14 means touching almost every file.
• The bot depends on an outside service or API that no longer exists.
• It lives in a no-code builder, where there is no code to repair.
• It only does what an off-the-shelf bot already does. Then the cheapest fix may be no custom code at all: BotGhost's free plan includes 8 custom commands and 3 events, and its paid plans cost $60 a year for one bot or $120 for unlimited bots, as of September 2026.

When a rebuild does make sense, it's priced on the normal ladder: a Starter bot from $590 covers one system with up to about 5 slash commands, and a Community bot from $1,490 covers up to 3 systems with a database and one integration. The $249 Bot Blueprint turns the old bot into a written spec with a fixed quote, and it's credited in full if you order the build within 30 days. The cost guide shows where those numbers come from.

What I need from you

1. The code. An invite to the GitHub or GitLab repository, or a zip of the project. Read access is enough to diagnose.
2. How it runs. The host, the start command, the Node.js or Python version, and the names (not the values) of the environment variables.
3. What's wrong. The error text or a screenshot of the log, when it started and which commands fail.
4. Not your token. Never paste a bot token into a chat, an email or a form. Anyone who has it can run code as your bot in every server it's in. If you already sent it somewhere, reset it under Bot > Reset Token in the Developer Portal; the old token stops working immediately. My Discord bot token guide covers what else to do after a leak.

I reproduce and fix the problem with a test application of my own in a private test server, so I never need your token. When the fix is ready, you put the token into your host's environment variables and restart, and I check with you that it's back. If you want me to deploy it, invite me as a user on your host if it supports that, rather than sharing your password. If a Developer Portal setting needs changing, such as a privileged intent, I tell you exactly which switch to flip.

What you get back

• The fix in your repository, as commits or a pull request, with library versions pinned so the next fresh install gets the same versions that worked.
• A short written report: what was wrong and why, what I changed, how to check that it works, what is likely to break next (such as the November 16, 2026 channel change, or discord.js deprecations that stop working in v15), and anything I noticed but didn't touch, like a token sitting in the git history.
• If it couldn't be fixed: a note on what I found and what a rebuild would involve, and no charge.

How I fix your Discord bot

1. Brief. Request a rescue with what the bot does, what broke and when, where it runs and how I can get the code.
2. Fit check. I look at it and confirm it's a rescue, or tell you what it is instead, before you pay anything.
3. Invoice. $149, paid up front. Invoices come through Stripe and can be paid by card.
4. Fix. Within 3 business days, tested on my own application in a private server.
5. Back online. You deploy with your token, or I deploy on your host account, and we confirm it works.
6. No fix, no fee. If I can't fix it, I refund the $149 in full.

Fix it yourself, hire a freelancer or use Bot Rescue?

I've built Discord bots since 2019. My first ones ran on discord.js v11 and v12, and the bots I build now run on discord.js 14, including the Discord operations for Rivals League's 154 teams. A ticket bot I built for an esports tournament organizer has its own repair toolkit because its SQLite database hit real corruption errors, so I've dealt with these failures from the maintainer's side too.

After the fix

A bot that broke because nobody was watching it will break again the same way. Care costs $49 a month and covers managed hosting, uptime monitoring, security and library updates when Discord changes things, daily database backups and one small change a month. Care Plus at $149 a month adds up to 2 hours of changes a month, replies within 1 business day and a monthly health report. Both are optional, billed monthly, and you can cancel any time.

Ready when you are: request a rescue and tell me what broke.