search

discord / discord-api-docs

Official Discord API Documentation
https://discord.com/developers/docs/intro
Other
5.95k stars 1.26k forks source link

When bots create a guild, it does not add the application.commands scope. #5540

Closed dynamicbark closed 2 years ago

dynamicbark commented 2 years ago

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

Steps to Reproduce

curl -XPOST 'https://discord.com/api/v10/guilds' -H 'content-type: application/json' -H 'authorization: Bot [token]' --data-binary '{"name":"test"}'

(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

typpo commented 2 years ago

@MichailiK this will be fixed in the next api deploy