> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vetox.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom Bot

> Run Vetox under your own bot name, avatar and profile. An add-on for Max and Black.

Every Vetox feature, running under **your** bot account — your name, your avatar, your status.

<Info>
  Available on **Max** and **Black** as an add-on: **Max+** and **Black+**. See [Server Premium](/en/premium/overview) for prices.
</Info>

<Warning>
  **Custom Bot does not grant AI access.** It is a separate flag from your tier, and AI is gated on the tier alone. **Max+ has no AI.** Only Black and Black+ do.
</Warning>

## What changes

|                          | Effect                                                                           |
| ------------------------ | -------------------------------------------------------------------------------- |
| **Name, avatar, banner** | Your bot's own                                                                   |
| **Description**          | Up to 400 characters                                                             |
| **Status**               | Playing, Watching, Listening or Competing                                        |
| **Slash commands**       | Registered on your own application                                               |
| **The public Vetox bot** | **Goes silent in that server** — it stops responding so the two never both reply |

<Note>
  Discord does not let bots use a plain custom status. Your status must be one of the four activity types.
</Note>

<Note>
  Identity updates are additive. Clearing a field leaves the previous value rather than removing it — set a replacement instead.
</Note>

## One server per bot

<Warning>
  A Custom Bot serves **one server**. On startup it leaves any other server it has been added to.

  Do not use the same bot application across several communities.
</Warning>

## Setting it up

<Steps>
  <Step title="Create a Discord application">
    In the Discord Developer Portal, create an application and add a bot to it.
  </Step>

  <Step title="Enable the privileged intents">
    **Server Members**, **Presence** and **Message Content** are all required. Without them the bot cannot start.
  </Step>

  <Step title="Copy the token and submit it">
    Paste it into the dashboard. Vetox validates it against Discord before accepting.

    <Warning>
      **The token is write-only.** Once submitted you cannot read it back from Vetox. Save your own copy first — if you lose it you will have to regenerate it in the Developer Portal and submit the new one.
    </Warning>
  </Step>

  <Step title="Invite your bot to your server">
    Using your own application's invite link, with the permissions Vetox needs.
  </Step>

  <Step title="Wait for it to come online">
    It starts within moments. The public Vetox bot then stops responding in that server.
  </Step>
</Steps>

<Note>
  Your token is encrypted at rest. Vetox validates the format, confirms it belongs to a bot account, checks the application, and verifies the three required intents before accepting it.
</Note>

## Transferring to another server

Moving a Custom Bot is a two-step confirmation, and the request expires after **30 minutes**.

<Warning>
  A transfer is final once confirmed. The bot leaves the old server and the public Vetox bot resumes there.
</Warning>

## Disabling

Disabling stops the bot and **clears the stored token**. Your branding settings and the audit log are kept.

To re-enable, submit the token again.

## If it crashes

A bot that crashes three times within a minute is stopped automatically to protect the platform. Fix the cause — usually a revoked token or missing intents — then re-enable it.

## Troubleshooting

<AccordionGroup>
  <Accordion title="The bot will not come online">
    All three privileged intents must be enabled in the Developer Portal: Server Members, Presence and Message Content. This is the most common cause.
  </Accordion>

  <Accordion title="Both bots reply to everything">
    The public bot goes silent only in the server the Custom Bot serves. If you see both, the Custom Bot may not have started — check its status in the dashboard.
  </Accordion>

  <Accordion title="I lost my token">
    Vetox cannot show it to you. Regenerate it in the Developer Portal and submit the new one.
  </Accordion>

  <Accordion title="My bot left a server on its own">
    Expected — a Custom Bot serves one server and leaves the others at startup.
  </Accordion>

  <Accordion title="I am on Max+ and AI is locked">
    Correct. Custom Bot is not a tier change; AI requires Black.
  </Accordion>

  <Accordion title="I changed the avatar and the old one is still showing">
    Discord caches bot avatars aggressively. Give it time before re-submitting.
  </Accordion>
</AccordionGroup>

<Card title="Manage Bots" icon="gauge" horizontal href="/en/account/manage-bots">
  The dashboard page where this is configured.
</Card>