Allow Slash Commands with message replies

[thecodrr]

Description

Currently it is not possible to use slash commands while replying: the command executes independently. It would be nice for Discord to send the messageId of the selected message with the interaction.

Why This is Needed

Various use cases:

1. Bots that provide message formatting helpers (like the /me built-in command).
2. It would be really helping for reporting certain messages.
3. It would help in support guild-specific message management features like maybe marking something as completed/deleted etc.

Alternatives Considered
One alternative is to use the "Copy ID" feature to send the message ID as an argument. However that isn't available unless you enable Developer Mode so increases user hassle.

Additional Details

[zeel01]

Not to mention that in the alternative case, you must make the argument a string and validate it yourself. So the user experience is poor, and it's more work to ensure that you are getting valid input.

Being able to reference a message in a command would be extremely valuable:

• Moderation tools: /report, /delete, /pin, etc.
• Q&A Helpers: Trigger a search for a topic on your Wiki by replying to someone's message with a /search command.
• Attachments: A work around for not having an attachment argument type, simply respond to a message with an attachment in it.
• "Thank you" system: Reply with a /thanks to give someone points ⭐
• Reminder bot: /remind me about this message later.
• Announcement bot: /send the contents of the selected message in my announcement channel at a scheduled time.
• Etc.

The potential uses are endless.

[advaith1]

just wanted to mention that adding context (right-click) menu items is planned and were in the figma prototypes, once that releases it'll be a better solution for message actions than reply slash commands

[zeel01]

Ah, well that's something to look forward to. Though I think reply slash commands would still be quite valuable.

[kberg]

I was just in the middle of writing such a bot, and see that it's not possible. Too bad.

[AlmostSuspense]

message context commands have been available for a very long time now, this should cover most of your needs

[zeel01]

Be that as it may, there are some workflows for which this suggestion would make more sense. Furthermore, depending on how someone has structured the design of their bot, it might be a little weird for 99% of features to be /slash commands, and only 1% of them be context commands. Also, I feel like users are generally not well educated on the existence of context commands - discovery just isn't as obvious and they're hidden in the submenu that many users probably won't recognize.

Over all, this seems like it would still be a useful addition allowing for a greater breadth of workflows and a more customizable experience, while being a bit more directly visible to users.