Start Application Commands via Buttons #3929
Replies: 3 comments 10 replies
-
Great suggestion, but will be redundant with the "form interactions" that have been mentioned a few times as something they plan to implement (or at least have teased they want to do it) Discussion #3334 |
Beta Was this translation helpful? Give feedback.
-
For defaults, you can actually work with optional values and don't require them, if not defined parameters you load in standard parameters and instead of confirming the slash command you first serve a message with the buttons, place a default in the description of the command so people know what the default is... (This is already possible today) For starting a slash command with a button i would rather say to just link it to the attachment button or new button in the default UI. I do love the idea of default parameters, but i rather have discord to not sort the values themselves in the option selectors so as bot developers you can adjust commands based on popularity once every 24h... , or place the default value at the top, making it, even more custom and easy to use. |
Beta Was this translation helpful? Give feedback.
-
I proposed something similar to discord when Context Menus were being released, which didn't make it through sadly. On top of buttons starting slash commands, imo a cool thing would be for Context Menus to initiate Slash commands. In fact, Context Menus are basically Slash commands at its core just limited to 1 parameter. Anything you can do in a Context Command you can do in a Slash command. But that could have been a huge way to expand user experience imo. For example, a poll or giveaway or reaction role or whatever command you have that requires a Message ID you could make a Context Menu for users to simply right click and initiate this command and the message id would be prefilled. This way end users would never need to have to enable developer mode to copy message ids. Click a message click Create Reaction Role > slash command options open with the message id parameter being prefilled. Too many times do bot support people need to teach users how to enable developer mode to get ids for things. |
Beta Was this translation helpful? Give feedback.
-
The Problem
Application commands are great, but I got the feedback that its hard for people to use them, especially on mobile devices, when there are lots of options.
With 25 options an application command can have, there is a lot to type when using the command.
A Solution
A solution for that problem could be buttons for application commands with pre filled values for options.
Example:
Given you have an application command
/some-command option1: someValue option2: someValue option3: someValue
You could have a Button "Start a Command!" and when the user presses the button, the application command UI opens for the command "some-command" and the options option1 and option2 are pre filled with default values.
Now, the user only has to fill in the value for option 3.
Code:
Style:
The Button Style could be similar to Link Buttons
Optional: A Modal to prevent abuse
It may be possible abuse this to make people invoke commands with values, they dont want to. To prevent this, a simple modal could help. But that's not really required because the user still has to press enter/send to execute the application command.
Benefits
Beta Was this translation helpful? Give feedback.
All reactions