Easier searching for slash commands #3793
Unanswered
RivenSkaye
asked this question in
API Feature Requests & Ideas
Replies: 1 comment 2 replies
-
To be honest I think this suffers from the same problem as #3744, as the purpose of application commands is that it should be intuitive to the user, and especially on mobile, people won't want to type in /; or other special characters. I believe there is a psuedo-workaround, as you could prefix bots with |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
There was a proposal for customizing prefixes for the Interactions API (topic #3744) which had a flaw pointed out regarding the UX suffering from it.
I do feel like there's room for improvement in the slash command interface though, especially when several bots register slash commands in a server and those in the latter half of the alphabet get pushed all the way down. Something that the old format of using prefixes didn't suffer from. For example take a bot currently sporting the prefix
;
, if you need to know what commands the bot offers just send;help
and there's a readable list in the chat. Sure, slash commands can include a/help
detailing the options, but then you'd need to scroll down to search and select the one for the right bot.The proposal I have takes the custom prefixes or grouping idea from the old bot format as an optional field for registering the commands, changeable by any member of a guild that has the relevant permissions (Manage Server for managing bots if I'm not mistaken). Rather than replacing the new global prefix
/
, I propose being able to combine this grouping to ease the search for the desired bot. One could type/;
and get the list of commands for bots, filtered to those that group under the semicolon.Naturally this also needs some form of restriction, since it would come with a lot of difficulties to implement if the grouping can be any arbitrary string (we wouldn't want a 1k char long prefix for example). For this I'd say allowing groupings of one or two characters in length that may not end in an alphanumeric character. This would allow a simple regex to be applied for finding the grouping, something like
/\/(.?|[^a-zA-Z0-9]){1,2}/
which would aid in getting the commands for a specific bot tremendously while allowing keyboard-only input that doesn't require holding down or mashing an arrow key.edit: fixed the regex to allow max 2 chars, previous version went up to 3
Beta Was this translation helpful? Give feedback.
All reactions