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

Discord does not let bots use a plain custom status. Your status must be one of the four activity types.
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. On startup it leaves any other server it has been added to.Do not use the same bot application across several communities.

​
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

Invite your bot to your server

Using your own application’s invite link, with the permissions Vetox needs.
5

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 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

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.
Expected — a Custom Bot serves one server and leaves the others at startup.
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.