Custom bot prefix for bots, as an better alternative to slash commands for now? #4367
-
While slash commands are still coming out, it's a huge step from a prefix based command handler, and I can say that it's pretty much hard to make a slash command handler with the popular libs, it's not their problem, but slash commands are made to be a lot different from message.content based implementation. While you all can definitely say slash are good, but it's still in its early stages and I think it's not much good than the nostalgia message prefix. Since the whole point of slash commands being to just not allow bots to read messages, couldn't we have another, simpler alternative to slash commands? Custom prefix registering (both globally and per server)? Why did I thought of this idea? Because taking the look at discord blog, they said the bot can still read messages from dms and pings, so if pings can be done, why not implement prefix based back again? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
This has been suggested many times before including in previous developer stages - the staff have ruled it out every time. They've cited (as you note) that bots can access their pings and DMs as well as the extra complexity of managing prefixes as their reasoning. |
Beta Was this translation helpful? Give feedback.
-
I guess I was late here to argue before slash came out, but I want to still argue about it. Bot prefixes were made so people and bots could differentiate bot commands from normal chats |
Beta Was this translation helpful? Give feedback.
-
The Discord staff have been very transparent about the reason behind the message intent behind for privacy and security reasons. I agree with the developers' response that applying for the intent "to make message commands still work" is and should remain invalid. I strongly believe that we'll be seeing most developers like myself transition over to interactions including application commands for the long-term future. While message commands may have their own benefits, an intuitive UX design far supersedes the need for the former in my eyes. |
Beta Was this translation helpful? Give feedback.
-
Duplicate of #3744 - custom prefixes aren't something we're exploring, for many of the reasons mentioned in that thread |
Beta Was this translation helpful? Give feedback.
Duplicate of #3744 - custom prefixes aren't something we're exploring, for many of the reasons mentioned in that thread