How to migrate away from ProBot
Move off ProBot without a gap in welcomes or levels — what transfers, what has to be rebuilt, and the image settings people forget to capture first.
Index
Every Discord guide and fix published by The Manual, newest first.
Move off ProBot without a gap in welcomes or levels — what transfers, what has to be rebuilt, and the image settings people forget to capture first.
Why Discord notifications are not arriving — seven causes common to all eight platforms, starting with the toggle that ships off and is easy to miss.
Set up Discord notifications from eight external platforms — the shared three-step setup every platform follows, and where each one actually differs.
Six scam patterns that account for nearly all of it, the three signals that identify every one of them, and what to configure so members meet fewer.
The error almost never means what it says. Here is how to find the real cause in under a minute, and the four things that actually cause it.
Discord has no appeals system, so every server builds one. The four decisions to make in advance, and the form that makes the rest straightforward.
The order that avoids downtime, what to inventory before Dyno's dashboard is gone, and why levels only need migrating if you were already paying for them.
Nine causes in likelihood order. The first is an exemption you set yourself, and the second is a wildcard that does not mean what it looks like.
Restrict Discord bot commands to specific roles or channels — per-command Enabled and Disabled lists, and how they differ from the Integrations page.
Nine controls in the order that matters, from the two Discord settings almost nobody changes to the audit-log layer that catches an insider.
Which permissions a Discord bot actually needs — a permission-by-feature table, the three riskier than they look, and why intents are not permissions.
Who to recruit, what to grant them, how to write the rules they enforce, and the three structures that stop a team burning out at the same point.
What to do about a Tagscript library that has no direct equivalent elsewhere, and the one category — ticketing — Carl-bot never built at all.
Move off Arcane without losing member levels — the inventory to take first, the order to move in, and why role rewards are the part that needs planning.
The first ten minutes decide how much you lose. Stop the access, establish who did it, restore structure, then close the route they used.
Which events are worth logging, how to route them without creating 148 channels, and why Discord's own audit log is not a substitute for this.
Are Discord bots safe? Mostly yes — the risk is rarely the code but the permissions you grant, the invite link you clicked, and an app nobody reviews.
Six causes, in order. The first one is right about three times in four, takes ten seconds to check, and produces no error message at all.
Why a Discord bot is not responding — nine causes, ordered by how often they are the answer, starting with a channel overwrite silently swallowing it.
What to do when a Discord bot goes offline — telling in ninety seconds whether it is Discord, the bot, one shard or your server, and how to stay safe.
Position beats permission. Almost every confusing permission problem on Discord comes down to that one rule, and it is not the rule most people expect.
Migrate away from MEE6 without downtime — the order to move in, the inventory to take first, and why kicking the bot does not cancel the billing.
The built-in AutoMod handles more than most people realise, and configuring it badly is worse than not configuring it. Here is the order to do it in.
Set up a Discord ticket system in thirteen steps, in dependency order — channel structure, intake forms, routing, claiming, limits and transcripts.
Switch Discord bots without losing member XP — the one free importer that genuinely moves levels, the parallel run, and seeding the ladder by hand.
Protect a Discord server against raids in three layers — what to configure before it happens, and what to do in the first sixty seconds when it does.