-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace CommandsNext with Discord’s slash commands #11
Comments
It is not implemented yet in DSharpPlus and I am not sure if it will be on my radar if it gets implemented. There’s not a lot of use for it since most commands are restricted to moderators, so they don’t have to be constantly available. |
Added DSharpPlus' official slash command module - see #12 |
I am not sure that working on this issue has value to moderators, who are currently (2021) using DiscordWikiBot’s commands most often. If there were more commands for regular users, then (There are also issues with how Discord implemented slash commands, for example requiring new permissions for bots for them to work, so it is tedious to seek to implement them now in any bot that was created before they became a thing.) |
One minor step towards adding this - if this might eventually become a thing - would be to start requesting the slash commands permission when adding the bot to new servers. It's not a particularly dangerous addition and would make the transition slightly easier. |
Good idea, yep. The code would still need to support both methods, though, since bot commands should not become unusable on any server just because Discord made a thing. Also, to clarify above a bit: I would be open to slash commands PR if it will be written with all the necessary precautions about adding them. This is why this is not a closed issue. For future me/others: the stuff I described about authorisation is from the official docs (403 errors will be thrown if bot tries creating commands on servers without necessary permissions) |
I’m not sure if it’s currently available for the library this bot is using, but a slash command option could be implemented.
The text was updated successfully, but these errors were encountered: