A Custom Bot runs Modora on your own Discord application. Your community sees your bot name, avatar and branding instead of Modora's, while every module keeps working exactly as it does on the main bot.
The Custom Bot is not sold. It is a Community Sponsor perk on Patreon, granted to verified patrons.
Your Own Identity
Bot name, avatar and application are yours; you create them in the Discord Developer Portal.
Branding
Set a banner and an embed footer that appear on the messages your bot sends.
Presence
Choose the status and the activity type and text your bot shows in Discord.
Own Instance
Your bot runs on its own token, separate from the main Modora instance.
The Custom Bot is a Community Sponsor perk on Patreon. You request it from the server you want it on; there is nothing to buy in the dashboard.
Become a Community Sponsor on Patreon
Link your Discord account on Patreon. That link is what lets us verify the pledge without asking you for anything.
Request it from your server page
Open the server in your dashboard and use the Custom Bot card. If we can match your Discord account to an active pledge that qualifies, the request is approved the moment you submit it.
Or let staff verify it by hand
If your Patreon is not linked to Discord, enter the email registered on Patreon and confirm you are a Community Sponsor. Modora staff check it and enable the Custom Bot for you.
One server at a time
An automatic grant covers one server. If you want the Custom Bot on a different server, the grant on the previous one has to be released first.
Custom Bot configuration lives on the Development Portal at dev.modora.gg, under Servers, Custom bot. The Custom Bot page in the main dashboard sends you there.
What you can set there
- Bot name and avatar
- Application id and bot token
- Banner image
- Status, activity type and activity text
- Embed footer
Modora does not create the Discord application for you. You create it yourself in the Discord Developer Portal, so the bot and its token stay in your own account. It takes a few minutes and needs no code.
Sign in to the Discord Developer Portal
Go to discord.com/developers/applications and sign in with the Discord account that should own the bot. Whoever owns this account owns the bot.
Open the Discord Developer PortalCreate a new application
Click "New Application", give it a name and accept the developer terms. This name is the application name; the username your members see is set later on the Custom bot page.
Open the Bot tab
In the left menu of your application, open "Bot". New applications already have a bot attached. If you still see an "Add Bot" button, click it and confirm.
Copy the bot token
On the Bot tab, click "Reset Token" and copy the token that appears. Discord shows it only once. Keep it to yourself: anyone with the token can control the bot.
Copy the application id
Open "General Information" and copy the Application ID. You need both the token and this id on the Custom bot page.
Turn on the privileged intents
Still on the Bot tab, switch on the privileged gateway intents described in the next section. Without them the bot cannot start.
Public Bot toggle
On the Bot tab you can leave "Public Bot" off. With it off, only you as the application owner can add the bot to a server, which is usually what you want for a bot that runs on your own server.
Discord keeps three data streams behind a switch: Presence, Server Members and Message Content. Discord does not send them until you turn them on for your own application, and no setting in Modora can turn them on for you. This is the step people miss most often.
You find them in the Discord Developer Portal, in your application, on the Bot tab, under "Privileged Gateway Intents".
Without these intents the bot stays offline
Modora asks Discord for the Server Members and Message Content intents at login. If your application does not allow them, Discord refuses the connection and your bot never comes online. It is not a Modora error, and no amount of restarting fixes it until the switches are on.
Set them like this
- Server Members Intent: ON. Required for joins and leaves, so welcome messages, join roles, Join Guard, invite tracking and member counters.
- Message Content Intent: ON. Required to read message text, so anti-scam, the link blocker, auto responders, leveling, counting and message logging.
- Presence Intent: not needed. Modora sets its own status and does not read member presences, so you can leave this one off.
Discord saves these switches per application. Set them before you start the bot, or restart the bot afterwards.
Bots in more than 100 servers
Discord requires bot verification before a bot in more than 100 servers may keep using privileged intents. A custom bot normally runs on your own server, so this does not apply.
Open the Custom bot page
Go to dev.modora.gg, pick your server under Servers and open Custom bot.
Paste the credentials
Paste the application id and the bot token into their fields.
Set name, avatar and presence
Fill in the bot name, avatar, banner, status and embed footer you want your members to see.
Save
Saving starts the provisioning; the bot is started for you. If you changed the intents afterwards, use Restart on the same page.
Invite your bot
Once the bot is active, use "Invite your bot" to add it to your server.
The Custom bot page shows an error and the bot stays offline
The bot is online, but does not respond to messages
Welcome messages and join roles do not fire
Invalid token
Name, avatar, banner, status, activity and embed footer are all set on the Custom bot page. The preview next to the fields shows how Discord will render it.
Tip
Changes to name, avatar and presence are pushed to Discord when you save.
Your bot token is stored server-side and is never returned in API responses.
The Discord application stays yours. You can regenerate the token or revoke access at any time from the Discord Developer Portal.
Yes. Both bots can sit in the same server and share the same configuration and data.