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

Using your own application’s invite link.
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 or Competing — Discord does not allow bots a plain custom status.
Branding updates are additive. Clearing a field leaves the previous value; set a replacement instead.

​
Transferring

Two-step, and the request expires after 30 minutes.
Final once confirmed. The bot leaves the old server and the public bot resumes there.

​
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 in a minute stops it automatically. Fix the cause — usually a revoked token — then re-enable.
Correct. Custom Bot is not a tier change — AI requires Black.
Expected. A Custom Bot serves one server.

Custom Bot

What it is and what changes.