Skip to content

Own bot problems

Your own bot says the token is invalid, an intent is missing, it does not respond, commands show twice, or you removed the main Clanzy bot? Causes and fixes.

What you seeThe own bot Squad VN Bot of Squad VN cannot log in anymore (its token was reset or deleted). Clanzy covers the server meanwhile.

Invalid or reset token

What you see: the server owner gets a direct message: "The own bot … cannot log in anymore (its token was reset or deleted). Clanzy covers the server meanwhile." The dashboard shows the token as invalid.

Why: someone pressed Reset Token in the Discord Developer Portal, the application was deleted, or Discord reset the token because it leaked.

Fix:

  1. Open the Discord Developer Portal, pick your application, Bot tab.
  2. Press Reset Token, then Copy.
  3. Paste the new token into the Own bot section and press the check button.

Meanwhile the main Clanzy bot serves your server, so members notice nothing. Step-by-step pictures: Your own bot.

A privileged intent is missing

What you see: the dashboard refuses the token and says Server Members or Message Content is off.

Fix: on your application's Bot tab, under Privileged Gateway Intents, turn on Server Members Intent and Message Content Intent, press Save Changes, then check again in the dashboard. Bots in fewer than 100 servers need no approval from Discord.

Your bot does not respond

Check in this order:

  1. Is the bot in the server? With a valid token but no invite, the main Clanzy bot keeps working. Press the invite button in the dashboard.
  2. Is the Own bot plan active? When it ends, your bot pauses. See the Billing section.
  3. Is its role high enough? Your bot's role must sit above the roles it gives, just like Clanzy's. See Bot role too low.
  4. Can it see that channel? Private channels need View and Send permissions for your bot's role.
  5. Check the status page if everything looks right.

Commands show twice

When you type /, you see the same command from Clanzy and from your bot. That is normal: Discord lists the commands of every bot in the server. Pick your bot's. Running a main Clanzy command only replies: "This server uses its own bot, … Please use …'s commands."

To tidy the list, go to Server Settings → Integrations → Clanzy and turn Clanzy's commands off for everyone. No member loses anything.

Double welcomes or rooms

This should not happen: the main Clanzy bot is quiet while your bot is active. If you see doubles right after the invite, wait a few seconds for the handoff to finish. If it continues, check whether another welcome or temp voice bot is in the server, then get help.

You removed the main Clanzy bot

The dashboard still works and your bot still does everything. But if your bot's token breaks, nothing steps in. The owner also gets: "Note: the main Clanzy bot is not in the server, so it cannot cover. Invite Clanzy again or paste a new token."

Fix: paste a new token, or invite Clanzy again from the add-the-bot page. Inviting it again loses no settings.

Frequently asked questions

I pasted the token into a chat channel. What now?

Delete the message, open the Discord Developer Portal, Bot tab, press Reset Token and paste the new token into the Own bot section of the dashboard. The old token stops working as soon as you reset it.

Why do I see every command twice when I type /?

Both the main Clanzy bot and your bot have commands. Pick the one with your bot's name; the main bot's commands only point you to your bot. To tidy up, hide Clanzy's commands in Server Settings, Integrations.

Does my bot come back by itself after a fix?

Yes. Once you paste and check a new token, your bot logs in again and takes over within seconds, with the same settings.

Updated