How to Run Two Discord Bots Without Them Conflicting (Roles, Welcome, Leveling)
To run two Discord bots without conflict, give each bot one job and turn off the overlapping features in the others. The three things that collide are welcome messages, auto-roles, and leveling — disable duplicates in every bot except the one you've chosen to own each task, then fix your role hierarchy so the right bot can actually assign roles.
Most server owners don't add a second bot on purpose. It happens by accident. You install MEE6 for leveling, then a friend recommends Carl-bot for reaction roles, then you bring in Dyno for moderation — and suddenly new members get welcomed twice, two bots fight over the same role, and your XP messages double up. Here's exactly why it happens and how to stop it, step by step.
Why stacking MEE6 + Carl-bot + Dyno causes conflicts
The problem isn't that these bots are badly built. MEE6 has the most recognizable leveling system. Carl-bot has the best reaction-role editor. Dyno is cheap and reliable for moderation. Each one is good at its thing.
The conflict comes from overlap. Every one of these bots ships with welcome messages, auto-roles, and leveling turned on or one click away. So when you run all three, you're not combining three different toolsets — you're running the same three features three times. Discord doesn't coordinate between bots. If MEE6 and Carl-bot both have a "give role X on join" rule, both fire. If two bots both post a welcome embed, the new member sees two.
There's also a real performance and management cost to running a thick stack of overlapping bots, which we cover in more detail in whether too many Discord bots slow down your server. For now, the practical fix is to make sure no two bots are ever doing the same job.
The 3 places bots collide: welcome messages, auto-roles, and leveling
Before you touch any settings, it helps to know that almost every multi-bot conflict falls into one of three buckets:
- Welcome messages and join DMs — two bots greeting the same member, or two DMs landing in their inbox.
- Auto-roles and role rewards — two bots assigning roles on join or on level-up, sometimes the same role, sometimes conflicting ones.
- Leveling and XP — two bots tracking XP on the same messages and both announcing level-ups.
Fix these three areas and you've handled the large majority of "my bots are fighting" problems. What's left is role hierarchy, which is its own step below. Let's go through each.
Step 1: Stop double welcome messages and DMs
Pick one bot to own welcomes. That's the whole strategy — one owner per feature. Then go into every other bot and switch its welcome system off.
- In MEE6: open the Welcome plugin and toggle it off entirely if MEE6 isn't your chosen welcome bot. Don't just clear the message text — an empty welcome can still trigger an auto-role.
- In Carl-bot: the welcome system lives under Greet. Set the channel to none or disable the greet message for that server.
- In Dyno: Welcome is a module you can fully disable from the dashboard module list.
The same logic applies to join DMs. If two bots both DM new members, people get two welcome DMs back to back, which reads like spam and is a common reason members mute or leave a server early. Decide which single bot sends the DM and disable the DM option in the others.
A quick test: have a friend join on an alt account, or use your own. You should see exactly one welcome in the channel and at most one DM. If you see two, you missed a toggle somewhere — go back through each bot's dashboard.
Step 2: Fix role-hierarchy fights (which bot wins)
This is the conflict that confuses people most, because it doesn't show up as a duplicate — it shows up as a bot that "just doesn't work."
Discord has one ironclad rule: a bot can only assign or remove roles that sit below its own highest role in the server's role list. If your Carl-bot role is below the "Member" role it's trying to grant, it silently fails. If MEE6 and Dyno both manage roles but sit at different heights, the higher one can manage roles the lower one can't, and you get inconsistent behavior that looks random.
To fix it:
- Open Server Settings → Roles.
- Drag each bot's role above every role that bot needs to manage. If a bot hands out @Level 10, @Verified, and color roles, its own role must sit above all of them.
- Keep bot roles below your staff/admin roles so a bot can never grant someone power over your moderators.
- If two bots manage the same roles, put the owner bot for that feature higher, and ideally remove role-management permission from the other one entirely.
The cleanest version of this is to not have two bots managing the same roles at all. We go deeper on this in what permissions to give a Discord bot, but the short rule is: only the bot that owns a feature should have the permission for it.
Step 3: Turn off duplicate leveling and XP announcements
Leveling is the single worst offender for duplicates, because XP is awarded on every message. If two bots both track XP, every active member is being counted twice, and you'll get two separate leaderboards that disagree with each other — plus two "you reached level 5" messages on every level-up.
Pick one leveling bot and shut leveling off everywhere else:
- MEE6: disable the Levels plugin if MEE6 isn't your XP bot.
- Carl-bot: turn off the Leveling/Automod XP module.
- Dyno + others: disable any ranks or XP module.
Then, in the one bot you kept, decide where (or whether) level-up announcements post. A lot of servers route them to a single #levels channel or set them to DM, so they don't clutter active chat. Two bots both announcing into #general is the fastest way to make level-ups feel like noise.
If your members already have XP history in two systems, accept that you'll lose one set when you consolidate — there's no clean way to merge two leveling databases. Better to pick the system you want and move on than to keep both running forever.
Step 4: Set the right permission order for your bots
Beyond the role-hierarchy fix in Step 2, audit what each bot can actually do. Conflicts often hide in over-broad permissions. A moderation bot does not need to manage your welcome roles. A leveling bot does not need ban permissions.
Walk down your role list and give each bot only the permissions for the features it owns:
- Moderation bot → Manage Messages, Kick, Ban, Timeout, Manage Roles (only for mute/punishment roles it controls).
- Welcome/role bot → Manage Roles (for join roles and reaction roles only), Send Messages.
- Leveling bot → Send Messages, and Manage Roles only if it grants level-reward roles.
Tightening permissions this way means that even if two bots overlap on paper, only one can actually act. It also reduces your security surface — fewer bots with Manage Roles or Administrator means fewer ways a compromised bot can damage your server.
When two bots are actually fine vs when to consolidate
Running two bots is not automatically a problem. It's fine when their jobs genuinely don't overlap — for example, a dedicated music bot plus a moderation bot, or a music bot plus an all-in-one community bot. Music is its own niche and most all-in-one bots don't do it, so that pairing rarely collides.
It becomes a problem when both bots cover general "community" features — welcomes, roles, leveling, moderation, tickets. That's where the overlap lives, and that's where you end up babysitting toggles forever. If you find yourself maintaining the same setting in two dashboards, that's the signal to consolidate. There's a good rule of thumb for the upper limit in how many Discord bots is too many.
Signs you should consolidate rather than keep tuning:
- You've disabled the same feature in two or three bots just to stop duplicates.
- A new member's experience depends on three dashboards all being set correctly.
- You can't remember which bot owns which feature without checking.
- Onboarding a new mod means explaining a stack instead of one tool.
Step 5: Replace the whole stack with one bot
The most reliable way to never have two bots conflict is to not run two bots. If a single bot covers your welcomes, auto-roles, leveling, moderation, reaction roles, and tickets, there's nothing to deduplicate — every feature has exactly one owner by default.
That's the case PeakBot is built for. It's a free, AI-powered Discord bot that replaces MEE6, Carl-bot, Dyno, and TidyCord with one tool, and it currently powers 500+ Discord communities. The features you'd otherwise stack three bots to get are all in one place and all free with no time limit:
- Welcome messages with embeds, DM, and auto-role — one system, one greeting.
- XP and leveling across message and voice activity, with leaderboards and role rewards.
- Context-aware AI moderation that reads message intent per channel instead of matching a fixed keyword list.
- Unlimited reaction roles, tickets, giveaways, polls, starboard, invite tracking, and full logging.
Because it's one bot, there's a single role to place in your hierarchy, a single permission set to manage, and no duplicate welcomes or XP messages to chase. For a side-by-side of moving off the classic trio, see how to replace MEE6, Carl-bot, and Dyno with one bot.
For pricing context: PeakBot's 30+ core features are free with no time limit, and Pro is $8.25/month per server (or $69/year). Compare that to stacking premium tiers — MEE6 premium at $11.95/mo, Carl-bot premium at $7.99/mo, and Dyno premium at $4.99/mo — where you'd pay three subscriptions and still have to manage the conflicts. You can see the full breakdown on the pricing page.
FAQ
Can two Discord bots do the same thing without breaking?
Technically yes — Discord won't stop them — but they'll produce duplicate output. If two bots both welcome members or both award XP, members see everything twice. Always assign one bot per feature and disable that feature in the others.
Which bot wins when two bots try to assign the same role?
Neither "wins" in the sense you'd expect — both will try, and each only succeeds if its own role sits above the target role in Server Settings → Roles. If a bot's role is too low, its attempt silently fails even though the other bot's worked, which is why role assignment can look random in a multi-bot server.
How do I stop getting two welcome messages in Discord?
Open each bot's dashboard and fully disable the welcome or greet module in every bot except the one you want to handle welcomes. Clearing the message text isn't enough — turn the whole module off, then test with an alt account to confirm you see exactly one greeting.
Is it better to run multiple bots or one all-in-one bot?
If the bots cover genuinely different niches (like music plus moderation), multiple is fine. If they overlap on community features — welcomes, roles, leveling, moderation — one all-in-one bot removes every duplicate and the maintenance overhead. See how many Discord bots is too many for where the line sits.
Will removing a second bot delete my server data?
Removing a bot stops it from acting, but roles it already created stay in your server until you delete them. Leveling XP stored in a bot's database is lost when you remove that bot, so export or screenshot any leaderboard you care about before consolidating.
