Slash Command Groups

[Cormanz]

Description

I'd like to be able to create multiple groups of Slash Commands for my bots.
This would be like the groups we already have for slash commands, where each bot has its own "group" of Slash Commands when you type / and see the auto-complete.

I'd like to be able to create multiple groups for my bot. My bot's a multi-purpose bot and having everything under one group means there's a lot of commands, almost too much

A step further, I'd even like to be able to only allow specific guilds to have access to a group, in-case you don't want to give all guilds access to each group

Why This is Needed

As I mentioned, a lot of bots are multi-purpose, so being able to divide your commands into groups would further improve the user experience
Also, it means bots with premium features can group their premium features so only guilds that have access to the Premium group can access it

Alternatives Considered

The only one I can think of is for these bots to be split into multiple applications so each different application has its own group, but I'm honestly not a fan of it

Additional Details

Nope

[Cormanz]

I also believe Slash Command Groups would be a better solution for use-cases like Premium commands then this issue

[UltimateSppy765]

Would you please mind explaining what you mean by slash command groups, I didn't really get your idea.

[Cormanz]

They're groups of commands under a specific label and icon that you can optionally lock to specific guilds

[UltimateSppy765]

Are they like:
/perms list
/perms edit

[Cormanz]

No, that's subcommands. Slash command groups are like icons/tabs in the commands menu, where top-level commands are. Like how multiple bots can have commands with the same name, because each command is in a different group.

[Cormanz]

copy paste 👎

?

[Dramex]

you can use Guild Slash Commands for cases like the one you mentioned.
https://discord.dev/interactions/slash-commands#create-guild-application-command

[GoldenAngel2]

you can use Guild Slash Commands for cases like the one you mentioned.
https://discord.dev/interactions/slash-commands#create-guild-application-command

Pretty sure you can't, it would result the same outcome as the one mentioned above.

[Dramex]

you can use Guild Slash Commands for cases like the one you mentioned.
https://discord.dev/interactions/slash-commands#create-guild-application-command

Pretty sure you can't, it would result the same outcome as the one mentioned above.

how so? you can enable commands on specific guilds using guild commands

[GoldenAngel2]

how so? you can enable commands on specific guilds using guild commands

1. It's a terrible experience for the end-user.
2. It's fairly annoying to work with guild slash commands for multiple reasons listed in the issues tab already.
3. What you suggested makes no sense for this feature request.
   -> To have slash command groups would be a better solution for multi-purpose bots and any bots that want their slash commands grouped up so it's easier for the end-user and developer to deal with.
   -> When you have to deal with which slash commands is enabled/disabled or not even there, it becomes really messy and a headache to deal with and there currently isn't a way to detect if the bot even has the OAuth2 scope on the guild itself unless you wish to make a request to get, post or put slash commands endpoint.

[Cormanz]

you can use Guild Slash Commands for cases like the one you mentioned.
https://discord.dev/interactions/slash-commands#create-guild-application-command

Guild-specific commands have rate-limits and for anything more then a couple dozen guilds you'll be rate-limited and unable to make more commands. Even if these were lifted, it'd still be a painful user experience.

Also, this still doesn't combat the problem of organizing your slash commands into sections.

[UltimateSppy765]

Guild wise permissions for global commands exist

[UltimateSppy765]

You can disable the premium only command ("default_permission":false) and then enable it for the premium guild using the everyone role ID for that guild (basically the same as that guild ID)

[SlipperySpelunky]

You can disable the premium only command ("default_permission":false) and then enable it for the premium guild using the everyone role ID for that guild (basically the same as that guild ID)

That still does not solve the slash command organization. What he means is something like this:

Administration:

 - /warn
 - /ban
 - /kick

Fun:

 - /meme
 - /dog
 - /cat

Of course, this would mainly be a visual request. However, it could potentially include the ability to sync permissions across each category, like how you can do in categorized text channels.

[Cormanz]

It's half visual, but there's also the benefit of locking specific groups to specific servers, like you could have a Premium group that only specific servers who payed to use your bot can access. The permissions idea is also good though.

[UltimateSppy765]

Oh I get it, that would be helpful yes. It would be interesting to see how permissions will work in that though.

[msciotti]

I'm not sure I fully understand. Permissions aside, could you explain how this would work differently than subcommand groups work today?

[Cormanz]

This is grouping commands visually, but the main thing is that you can lock commands between guilds. So, you could have a Premium group of commands that only guilds who payed for your bot's premium plan can use.

[Rapptz]

#3349 (reply in thread)

[UltimateSppy765]

I'm not sure I fully understand. Permissions aside, could you explain how this would work differently than subcommand groups work today?

As far as I understood, they meant allowing the developer to categorise the commands on the basis of their use, like:
Administrative:
/delete
/create... etc
Moderation:
/kick
/ban... etc

[Dramex]

i think what they mean is tags, ability to filter commands by a tag.

[typhoon11]

I have explained it better in #5052 so you can check that