Skip to main content
Every Vetox feature, running under your bot account — your name, your avatar, your status.
Available on Max and Black as an add-on: Max+ and Black+. See Server Premium for prices.
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.

​
What changes

Your bot’s avatar and banner accept an upload of up to 10 MB each — everywhere else on Vetox the limit is 3 MB.
Discord does not let bots use a plain custom status. Your status must be one of the five activity types. Streaming additionally needs a twitch.tv or youtube.com stream URL alongside the status text.
Identity updates are additive. Clearing a field leaves the previous value rather than removing it — set a replacement instead.

​
One server per bot

A Custom Bot serves one server — the one you authorized through Discord’s approval screen. It leaves any server it was added to without that approval.Do not use the same bot application across several communities.
Authorizing a new server replaces the previous one: the bot leaves the old server and stays only in the newly approved one. You do not need to be the Discord owner of the server — approving the invite is what grants it.

​
Setting it up

1

Create a Discord application

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

Enable the privileged intents

Server Members, Presence and Message Content are all required. Without them the bot cannot start.
3

Copy the token and submit it

Paste it into the dashboard. Vetox validates it against Discord before accepting.
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.
4

Register the Vetox redirect URI

Vetox shows you a URL on the Custom Bot panel. In your application’s OAuth2 settings, add it under Redirects and save, then press Re-check on the panel.
This step is required. Invite links stay disabled until the URL is registered, and Discord rejects any authorization that does not carry it.Vetox cannot add it for you — Discord lets an application’s redirect list be read but never written through the API, which is what stops a leaked bot token from being usable to hijack authorizations.
5

Invite your bot to your server

Use the invite link from the dashboard, not one you build yourself. It carries a single-use authorization that expires in 10 minutes and tells Vetox which server you approved.
6

Wait for it to come online

It starts within moments. The public Vetox bot then stops responding in that server.
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.

​
Transferring to another server

Moving a Custom Bot is a two-step confirmation, and the request expires after 30 minutes.
A transfer is final once confirmed. The bot leaves the old server and the public Vetox bot resumes there.

​
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 goes offline

A Custom Bot that loses its connection is restarted automatically, with a widening delay between attempts. Brief Discord outages and network drops recover on their own, and your bot stays in your server throughout — it is never removed because of a connection problem. Vetox only reports it as offline once several restarts in a row have failed. That normally means something only you can fix: a regenerated token, or a privileged intent switched off. Correct it in the Developer Portal and submit the token again.

​
Troubleshooting

All three privileged intents must be enabled in the Developer Portal: Server Members, Presence and Message Content. This is the most common cause.
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.
Vetox cannot show it to you. Regenerate it in the Developer Portal and submit the new one.
A Custom Bot stays only in the server you approved through Discord’s authorization screen. If it left one, that server was never approved — or you approved a different one afterwards, which replaces it.Re-invite it using the dashboard’s invite link and approve it on Discord’s screen. A link you assembled yourself carries no approval and will not keep the bot there.
The Vetox redirect URI is not registered on your application yet. Copy it from the Custom Bot panel into your application’s OAuth2 → Redirects, save, then press Re-check.
The URL was not saved on your application, or was saved with a typo. It must match exactly, including https:// and any trailing path. Copy it again from the panel rather than typing it.
Correct. Custom Bot is not a tier change; AI requires Black.
Discord caches bot avatars aggressively. Give it time before re-submitting.

Manage Bots

The dashboard page where this is configured.