Currently when a bot creates a guild, it will only authorize the bot with the bot scope in the guild, it will not authorize it with the application.commands scope. This is inconsistent with the oauth2 page, which forces the application.commands scope if you have the bot scope.
Currently I have to rely on the logic of the someone getting the admin permission so their client can run the migration whenever they choose to click on the server, and then go into settings to enable the integration for the @everyone role. (And I don't think the migration will be around forever.)
Description
Currently when a bot creates a guild, it will only authorize the bot with the
bot
scope in the guild, it will not authorize it with theapplication.commands
scope. This is inconsistent with the oauth2 page, which forces theapplication.commands
scope if you have thebot
scope.Currently I have to rely on the logic of the someone getting the admin permission so their client can run the migration whenever they choose to click on the server, and then go into settings to enable the integration for the
@everyone
role. (And I don't think the migration will be around forever.)Steps to Reproduce
(I didn't actually test if this command works, I'm just doing it from memory--but hopefully its enough information.)
Expected Behavior
When the guild is created, the bot gets the
application.commands
scope.Current Behavior
The bot only has the
bot
scope in the guild.Screenshots/Videos
No response
Client and System Information
n/a, its consistent across everything