Slash command prefixes #3744
-
|
The slash commands list on a server can get very cluttered. It will likely get even more cluttered as more bots implement slash commands in preparation for the intents change. This can make it hard to find the commands you need, especially if multiple bots have a command under the same name. My proposal is to have an option for a different prefix to slash commands, chosen either by the bot, the server, or a combination of the two. So for example, I (as a server owner) set "Bot A" to use the The list when pressing |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 15 replies
-
|
I personally feel like if this is added, it should be controlled by the bot, but also be able to be per server. that way we can have something similar to the old way of prefixes |
Beta Was this translation helpful? Give feedback.
-
|
How many bots do you have? Also, 99% of the bots I've seen haven't even implemented slash commands yet, so I don't see too much reason for concern. |
Beta Was this translation helpful? Give feedback.
-
As I said many bots that don't already have them will be adding them due to the upcoming intents change. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, but how many bots do you have? |
Beta Was this translation helpful? Give feedback.
-
|
Maybe this would be great for some select users, but its terrible for most. Part of the thinking behind slash commands is that users don't have to guess at what a prefix is for a bot. How does discord surface these other prefixes to users? And doing this makes it far less likely for users to find a command they are looking for using discovery. |
Beta Was this translation helpful? Give feedback.
-
|
plus people are used to custom prefixes, if anything itd be better cause people are used to it |
Beta Was this translation helpful? Give feedback.
-
|
Just because people are used to something doesn't mean it is a good experience. The amount of times people still use the wrong prefix for message commands is astounding. |
Beta Was this translation helpful? Give feedback.
-
As I said, the list when pressing
Could be some indication on the profile or in the
Yes, that's why |
Beta Was this translation helpful? Give feedback.
-
I think it would be terrible ux to see a menu with commands pop up everytime you type in a random special character. |
Beta Was this translation helpful? Give feedback.
-
|
Well, you could use multiple characters for a prefix, and prefixes are there because they are not used frequently in conversations. |
Beta Was this translation helpful? Give feedback.
-
|
There's a reason why it's called a slash command. Very straightforward. Perhaps it could just be a command explorer UI that has your suggestion placed. I don't see a specific reason though, you could still click the bot's avatar in the left side of the UI to start at the first command of the app and different prefixes could cause a misunderstanding since it's not uniformed. And I also agree with ckohen's statement regarding people using the wrong prefixes. |
Beta Was this translation helpful? Give feedback.
-
|
They aren't called slash commands anymore, they are now called application commands, and "slash commands" specifically are called chat input commands |
Beta Was this translation helpful? Give feedback.
-
|
True, but the application commands shown in the command list still are slash commands since they start with the forward slash character and are meant to be that way when they got released. |
Beta Was this translation helpful? Give feedback.
-
|
Slash commands (also known as chat input commands) are a type of application command, the terms are not directly equivalent. Regardless, the client still refers to them as slash commands and all of the branding around them uses slashes. This can of course be changed at any time, so terminology isn't really relevant to either side. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
What @ckohen wrote is pretty spot on - with frecency and other planned updates, navigating the list should become improved and faster over time. Those updates are a better target for dev time and effort than custom prefixes, which negate many of the user-facing improvements slash commands have 😄 |
Beta Was this translation helpful? Give feedback.
-
|
Can't it be configurable by the user (so they can enable, disable, or use both slash and custom)? For developers, it's a nightmare to have one prefix for all bots. |
Beta Was this translation helpful? Give feedback.
-
|
it was a nightmare that slash commands fixed |
Beta Was this translation helpful? Give feedback.
What @ckohen wrote is pretty spot on - with frecency and other planned updates, navigating the list should become improved and faster over time. Those updates are a better target for dev time and effort than custom prefixes, which negate many of the user-facing improvements slash commands have 😄