Docs

The dashboard, page by page

Custom bot

This text is the dashboard’s tour for this page.

1.Your own bot identity

By default the server is served by the JP Metamods application: its name and avatar. With this option it is served by an application of your own instead, with the same features and settings; only the identity members see changes. Business includes it; on Free or Pro it is an add-on.

2.Which bot serves this server now

The identity answering here, and whether it is online. With a custom bot set up, this card also says the next step: invite your bot, then remove the JP Metamods bot so members see one bot.

3.Application id and token

Create an application in the Discord developer portal, switch on the two privileged intents (server members, message content), paste the application id and the bot token here. The token is checked with Discord before it is stored (it must belong to that application), stored encrypted, and never shown again. A token that fails to log in shows as an error here and the server stays with the JP Metamods bot; a token that fails later is replaced here.

4.How it works

One process serves every server; a custom bot is a second Discord connection in it, running the same code. Disable keeps the token and hands the server back; Remove forgets the token.

4 settings explained

Add the bot, run the tour, invite your members

It takes one afternoon. The captcha, the roles and the welcome are waiting for them.