You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add a "Preparing your bot for public use" guide #531
I guess I did not get as far as I thought but still a good start:
Preparing Your Bot For Public Use
As you are adding the finishing touches to the first feature of your bot you may begin to think about how it will be used in production.
Depending on your goals you may not want make your bot open for public use. This is common for bots that are intended for specific servers.
To prevent unexpected usage ensure that the "Public Bot" setting in the "Bot" tab on the Dev Portal is toggled off.
Making Your Bot Public
The Dev Portal includes various settings that will make it easier for users to utilize your bot.
The first step is to ensure that the "Public Bot" setting in the "Bot" tab of the Dev Portal is toggled on.
Under the "Installation" tab in the Dev Portal you will find the Installation Contexts that your bot supports.
It is likely that during the development phase of your bot you configured these settings.
However, it is possible that they got changed so it is good to double check.
Make sure that if your bot does not support any of the installation contexts they are disabled.
This will help prevent confusing users if they accidentally install the bot to a context that is not supported.
Below those settings there is the "Install Link" setting. This controls a button on your bots profile within Discord.
When "None" is selected there will not be a button for users to add your app on your bots profile.
This does not mean that users cannot install the bot.
If you want to prevent users from installing your bot see the comments about the "Public Bot" setting.
When "Custom URL" is selected you will be prompted to input a URL.
You can put a URL to your website.
This option is only recommended if you need to do some sort of additionally processing before having the user install the bot.
An example of this would be generating custom invite links with different permissions depending on what modules a user wants to use.
The recommended method for most people is to use the "Discord Provided List" option.
This will make the button on your apps profile open the bot authorization flow directly.
This will enable a new section for "Default Install Settings".
The allows you to specify what scopes you want your bot to have.
At the time or writing user installed bots can only have the application.commands scope while guild installed bots can also have the bot scope.
Almost all guild install bots will need the bot scope, so make sure to enable it.
You would not need the bot scope if your bot does not need any information about the guild or does not perform any action on the guild.
After selecting this scope you will be prompted to select the recommended permissions that users should give your bot.
Select the permissions that your bot needs and then save your changes.
Growing Your Bot
App Verification
In order to increase the safety of the platform Discord applies restrictions to bots that are not verified.
The most notable of these restrictions is that your bot will be unable to join more than 100 servers.
Luckily verification is a straightforward process. This article by Discord explains how to verify your bot.
There are two things of note regarding app verification.
The first is that app verification is not required if you plan to keep your bot under 100 servers and do not need other features locked behind verification such as monetization.
Verification can be completed at any time so you can verify at a later point.
The second is a common misconception about verification.
Many Discord users attribute verified bots as more trustworthy then unverified bots.
This is a dangerous misconception as verification is self service and really only shows that Discord may be able to help in the event of a serious legal issue.
Marketing
There are two main ways to increase the number of users of your bot.
The first is through direct advertisement of your bot on Discords built in App Directory or 3rd party sites like Top.gg, and Discord Bot List.
Activity
Icebluewolf commentedon Aug 21, 2026
I have a rough draft for this. Will send it later today.
Icebluewolf commentedon Aug 21, 2026
I guess I did not get as far as I thought but still a good start:
Preparing Your Bot For Public Use
As you are adding the finishing touches to the first feature of your bot you may begin to think about how it will be used in production.
Depending on your goals you may not want make your bot open for public use. This is common for bots that are intended for specific servers.
To prevent unexpected usage ensure that the "Public Bot" setting in the "Bot" tab on the Dev Portal is toggled off.
Making Your Bot Public
The Dev Portal includes various settings that will make it easier for users to utilize your bot.
The first step is to ensure that the "Public Bot" setting in the "Bot" tab of the Dev Portal is toggled on.
Under the "Installation" tab in the Dev Portal you will find the Installation Contexts that your bot supports.
It is likely that during the development phase of your bot you configured these settings.
However, it is possible that they got changed so it is good to double check.
Make sure that if your bot does not support any of the installation contexts they are disabled.
This will help prevent confusing users if they accidentally install the bot to a context that is not supported.
Below those settings there is the "Install Link" setting. This controls a button on your bots profile within Discord.
This does not mean that users cannot install the bot.
If you want to prevent users from installing your bot see the comments about the "Public Bot" setting.
You can put a URL to your website.
This option is only recommended if you need to do some sort of additionally processing before having the user install the bot.
An example of this would be generating custom invite links with different permissions depending on what modules a user wants to use.
This will make the button on your apps profile open the bot authorization flow directly.
This will enable a new section for "Default Install Settings".
The allows you to specify what scopes you want your bot to have.
At the time or writing user installed bots can only have the
application.commandsscope while guild installed bots can also have thebotscope.Almost all guild install bots will need the bot scope, so make sure to enable it.
You would not need the bot scope if your bot does not need any information about the guild or does not perform any action on the guild.
After selecting this scope you will be prompted to select the recommended permissions that users should give your bot.
Select the permissions that your bot needs and then save your changes.
Growing Your Bot
App Verification
In order to increase the safety of the platform Discord applies restrictions to bots that are not verified.
The most notable of these restrictions is that your bot will be unable to join more than 100 servers.
Luckily verification is a straightforward process.
This article by Discord explains how to verify your bot.
There are two things of note regarding app verification.
The first is that app verification is not required if you plan to keep your bot under 100 servers and do not need other features locked behind verification such as monetization.
Verification can be completed at any time so you can verify at a later point.
The second is a common misconception about verification.
Many Discord users attribute verified bots as more trustworthy then unverified bots.
This is a dangerous misconception as verification is self service and really only shows that Discord may be able to help in the event of a serious legal issue.
Marketing
There are two main ways to increase the number of users of your bot.
The first is through direct advertisement of your bot on Discords built in App Directory or 3rd party sites like Top.gg, and Discord Bot List.
Branding
Error Handling
Providing support
Being Unique