Missing Features for Slash Commands

albedo

At the end of this year Discord released in my opinions one of the coolest features yet: slash commands.

However, in their current form they still lack some features. For one, there is no way to set permissions on Discord's side, leading to all commands being exposed to all users, which can pose a risk especially when moderation bots are involved. A solution would be for developers to set permissions on who can use what commands leaving only allowed commands exposed to the user.

Another thing that isn't really necessary, but would be a nice to have, is user only replies, similar to the built in slash commands.

10

Kommentare

3 Kommentare

Datum Stimmen
  • donovan_dmc

    Even if Discord provides checking for permissions on their side, all bots should still be checking them themselves. You could still manually send an interaction the bot, and possible bypass a lot of Discord checks, since most are client-side only.

    0
  • Marquardt

    In order to get Slash Commands up and running with your app, you'll have to create the command itself, then prepare your app to be able to handle the interaction flow. We'll describe that flow in more detail in the steps below, but the basic pattern is:

    • A user in Slack types in the message box with the command, and submits it.
    • A payload is sent via an HTTP POST request to your app.
    • Your app responds in some way.
    0
  • MightyWolf_
    • Bearbeitet

    For one, there is no way to set permissions on Discord's side, leading to all commands being exposed to all users, which can pose a risk especially when moderation bots are involved. A solution would be for developers to set permissions on who can use what commands leaving only allowed commands exposed to the user.

    Really missing this feature as well. Currently we have only a single bot that supports slash commands in our guild, but once more bots start migrating to this feature, this will become a real issue. E.g. I'd want a music bot to listen for messages in the text channel #music or #voice-text, but then there are other bots which make no sense to be there. Not to mention NSFW bots, which will be suddenly active outside NSFW channels? Seems like a big oversight to me or I'm really missing something.

    EDIT: Found an issue focused on this exact feature, so hopefully it'll get implemented soon *fingers crossed*.

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.