-
Notifications
You must be signed in to change notification settings - Fork 40
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
Convert !commands to slash commands #131
Comments
This seems like one benefit we'd get by updating discord.js, maybe that's a better title? |
I'm intentionally keeping this as a separate issue, since this is more of a UX improvement and the handler format is not required in discord.js 13. Neither PR has this yet, and I might move the refactor to another PR anyway to make it easier to review. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Renaming to specifically use slash commands, since we don't seem to need the other application command types (user and message context menu commands) yet. Slash commands are specifically used when typing messages, which is most similar to how we're currently using the bot. |
Ye, we need this |
What's the status of this? I noticed another PR got merged, but I'm not seeing our slash commands on Discord. |
I haven't made any changes to affect this, but I did implement command deployment in #198 which should facilitate this. Our only command atm is the anonymous report reactibot/scripts/deploy-commands.ts Line 27 in 7f3bbcd
|
Inspired by #46
Application commands provide a better UX for running bot commands in Discord (fixing common issues of ours like moderators having to delete commands that users accidentally run) while also allowing for more relaxed bot permissions.
Once we upgrade to discord.js 13, we can use their registering slash commands example.
The text was updated successfully, but these errors were encountered: