Application Command tags in messages

[ZeldaFan0225]

Application Command tags in messages

Short description

This could be a tag like @ or # mentions or dates where you can click it to see a full command including already filled out arguments.
This could be used by developers to provide support with their commands by sending sample commands and in bots to show how a command can be used or frequently used configurations (with filled out arguments).

Why this is needed

It would make the whole application command experience a significantly better because developers can just use that tag instead of fully writing out the command with (up to) 25 arguments.

[kingmigdor]

This is actually a cool idea. Maybe it would be possible to make a thing that enters the command automatically? Like when you click on the command tag, it shows the command in the slash commands window?

[ZeldaFan0225]

That was the idea kinda

[ZeldaFan0225]

Since this has now been implemented I am narrowing down this feature request to have prefilled arguments in the application command tag which would work like:

</NAME SUB_NAME [ARGUMENT:VALUE]:ID>

this would copy the prefilled arguments to the textbox.

This would be helpful for advanced moderation e.g. when you view a moderation case the developer could embed a command like
</REMOVECASE [CASE:12]:1234567890123456789> to easily remove the case without needing to search for a command and the case id

Or it can help the users with rather complicated inputs by prefilling it

also a preview of all prefilled arguments on hover would be neat

[Stalruth]

Another way to implement it without inventing a new syntax is using query parameters, so a command mention could look like </data:996947661854867477?name=Blaze>. totally original idea :mmLol:

Definitely seconding this though - it can help with migration as bots add commands and have to reorganise, and I believe @VelvetThePanda has some more complicated use-cases where other options don't quite work.

[xkasprx]

So many use cases that I can do if this idea is implemented in whatever method

[IanMitchell]

Can you expand on use cases?

[xkasprx]

So allowing this would allow for prefilled help commands.
Query the bot and they misuse the command, it can suggest what it should be, already filled out.
In an event system, where members join with slash command, that event command could be prefilled with the event number.
Ticket/bug systems could suggest reporting and autofill any errors that occurred (kinda lazy development but still an idea).
Closing a ticket/bug in a ticket system.
Suggestion management.

Those are just the ones I could personally use.

[ZeldaFan0225]

Can you expand on use cases?

Basically any follow up action which you want to have arguments on which are validated inside discord or have autocomplete or where the information is too much to get into a custom id of a modal (I wouldn't want to save a custom id of a modal in a database in case somebody in the future may want to follow up. This would allow for more flexible followup commands since modals only support plain text and basically no options you have available in slash commands.

For example when you created a moderation case and you want to edit the case e.g. the reason then you could partially prefill a command for the user to then fill in the correct moderator (slash command user field), a new reason (yes could be done with modals but you can autocomplete common reasons for faster usage of the command) or other type specific (like channel, role, number,...) data of the moderation case.

Another significant advantage over modals would be the ability to habe more than 5 fields