Skip to content
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

Slash command migration #210

Closed
eileenthg opened this issue Sep 25, 2022 · 3 comments
Closed

Slash command migration #210

eileenthg opened this issue Sep 25, 2022 · 3 comments

Comments

@eileenthg
Copy link

Discord as of today at least has completely moved to slash commands, meaning all text command (!get, !update etc.) no longer works. This is happening for all bots that uses text commands.

Slash commands announcement: https://discord.com/blog/slash-commands-are-here
Developer portal to port to slash commands: https://discord.com/developers/docs/interactions/application-commands

If anyone wants to continue using this bot we'll have to port slash commands over. Otherwise we'll have to look for alternatives...

@eileenthg
Copy link
Author

Nevermind I dumb mention the guy instead to trigger its commands.
So instead of n!get, you do @Niles get

@mchangrh
Copy link
Member

#193

It's not a simple port since Niles is built around message content. We got rejected the first time we applied for message content privileges and I don't have access to request a second time. I've tried porting before, see intents and v5 branches. If someone wants to take over that's fine with me

@mchangrh
Copy link
Member

closing as duplicate of #193

@mchangrh mchangrh closed this as not planned Won't fix, can't repro, duplicate, stale Jan 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants