Skip to main content
Where a Custom Bot is set up and controlled.
Requires Max+ or Black+. The page also lists your subscriptions.

​
The four-step setup

1

Create a Discord application

In the Discord Developer Portal, create an application and add a bot to it.
2

Submit your bot token

Paste it here. Vetox validates it against Discord before accepting.
The token is write-only — once submitted you cannot read it back. Save your own copy first.
3

Invite the bot to your server

Register the Vetox redirect URI shown on the Custom Bot panel under your application’s OAuth2 → Redirects, then invite the bot with the dashboard’s invite link — not one you build yourself.
4

Done

It starts within moments, and the public Vetox bot goes silent in that server.

​
What you must provide

All three privileged intents are mandatory. The token is rejected without them, and this is the most common setup failure.

​
Branding

Name, avatar, banner, a description of up to 400 characters, and a presence.
Presence must be Playing, Watching, Listening, Competing or Streaming — Discord does not allow bots a plain custom status. Streaming additionally needs a status text and a twitch.tv or youtube.com stream URL.The name and username cap at 32 characters and the status text at 128.
Emptying a field you had set removes it. An avatar, banner, description or status you clear here is cleared on your bot. A field you never set is left alone, so the avatar, banner or description from the Discord Developer Portal stays. The name is the exception: a bot always has one, so an empty name keeps the current name.What you set here is applied again each time you save and each time your bot restarts. Change these fields here rather than in the Developer Portal.

​
Transferring

Two-step, and the request expires after 30 minutes. You must own or administer the new server, and the public Vetox bot must already be in it. Your premium moves with the bot on confirm — the Active Server and the Custom Bot panel always name the same server — then invite the bot to the new server with the dashboard’s invite link.
Final once confirmed. The bot leaves the old server and the public bot resumes there.
If the new server already runs another Custom Bot or holds other premium, your subscription takes it over, and the subscriptions it replaces are released back to their owners, not cancelled.

​
Disabling

Stops the bot and clears the stored token. Branding and the audit log are kept — resubmit the token to re-enable.

​
Audit log

The last 50 actions on your Custom Bot.

​
Troubleshooting

Almost always a missing privileged intent. Enable all three, then resubmit.
Same cause, or the token was regenerated in the Developer Portal after you submitted it.
Three crashes within a minute trigger an automatic restart, never a shutdown — a repeatedly throwing handler is treated as a Vetox defect, not a reason to evict your bot. If the restarts keep failing the bot reports offline and a background reconcile keeps retrying, so there is nothing to re-enable. Check the token is still valid and that the three privileged intents are still on.
Correct. Custom Bot is not a tier change — AI requires Black.
Expected. A Custom Bot serves one server. It also leaves a server that another subscription’s Custom Bot takes over, and your subscription is released, ready to activate on another server.

Custom Bot

What it is and what changes.