Slash Commands Permission System - Hidden Commands, Global permission by User and Guild Permission

[Luc1412]

Manually moved issue #2920

Description

The permissions system needs 3 additions:

• Hidden option which completely removes the command from the command selection (instead of grey it out)
• Option to globally hide/show members by id (instead of doing it per guild)
• Option to (globally) show/hide a command by Discord guild permission (eg. on all servers where ppl. got "Manage Server" they are allowed to use command x

Why This is Needed

While implementing permissions into my bot I encountered multiple problems:

Owner only/Bot management commands:
I got a few bot management commands which should only be executed by a specific set of users. To benefit from the nice user experience I migrated my text to slash commands. My initial thought was to disable the command by default and just allow them to my list of owners. That turned out to be harder than expected.

1. I have to set the list of user ids for 50.000 servers + need to modify this list every time the bot joins a new server (massive payload -> wasted traffic)
2. The command still appears still in the other user's selection greyed out. -> they shouldn't know about them and they only disturb

My temp solution: Defining owner guild ids and just do this for a few servers.

Bot settings command:
I got a few commands which are used to set up the bot and modify the settings. I limit them to the following Discord Permissions: Administrator or Manage Server. That also turned out to be harder than expected. As the owner commands, I have to define it for all 50k guilds. For each guild, I need to check the roles and their permissions and list the right ones to Discord. I also need to edit this every time the bot gets added to a new server + every time a relevant role has been modified

[UltimateSppy765]

Hidden option which completely removes the command from the command selection (instead of grey it out)

The commands are actually supposed to be hidden instead of being greyed out iirc, for now they just grey out and it will probably be seen to in the future. As for the other stuff, we really need them, this will solve a lot of issues.
And I had considered the fact that using Discord permissions might interfere with role and user perms, modifying the roles that can use it could just probably be locked to roles that have that Discord permission.
For example I have a command locked to kick members permission, and I only want special roles to be able to use it, then it could be made so that Discord would only let me lock the command to roles/users who actually have that permission. Otherwise the command permissions could just be set to work like Channel Overrides, which is imo also perfectly fine.

[Ross-Esmond]

Do you have a source on that? It's not mentioned in the master list.

[ckohen]

The dev docs have this info block which suggests an intention to change it, and it would fall under the permissions revamp mentioned in t hat list

[Ross-Esmond]

If you do not have permission to use a command, we will remove it from your command explorer list (when you type /)

Nice, thank you.

[SirThrills]

For hiding commands users don't have permission to use, this is definitely a must have for servers with mod commands you don't want users to know about.

Ideally some kind of flag we can pass in like:
1 = hidden without permission
0 = greyed out without permission

[LugiaDepression]

They need to hide commants that people can't use. It's illogical to have them see them, forcing them to have senselessly long command list for unnecarly

[ooliver1]

You're both posting on a very old discussion, the new permissions system is already out.

[LugiaDepression]

@Smidul @ooliver1 The commands people have no permission to carry out by the original settings on the bot ARE showing up regardless of what you are stating. (This screenshot is from a regular user.)

[ooliver1]

@Smidul @ooliver1 The commands people have no permission to carry out by the original settings on the bot ARE showing up regardless of what you are stating. (This screenshot is from a regular user.)

Completely unrelated to what I said, a separate discussion or issue should be made as the permission system is entirely different.

[LugiaDepression]

@Smidul @ooliver1 The commands people have no permission to carry out by the original settings on the bot ARE showing up regardless of what you are stating. (This screenshot is from a regular user.)

Completely unrelated to what I said, a separate discussion or issue should be made as the permission system is entirely different.

This isn't a permission issue. They can't carry out the commands because the original permissions mods set to the bot so the bot just gives them an error message in reply BUT the commands are still showing up in the first place.

[onerandomusername]

If its the bot giving the error message, then contact the bot. The api supports hiding commands that users cannot use, but that requires setting up the bot with that system.

[typpo]

The new permissions system handles most of this feedback https://discord.com/developers/docs/interactions/application-commands#permissions

[LugiaDepression]

Dead commands are still showing up for regular users even if they can't carry them out by the original settings on the bot prevoiusly made before slash integrations.

[AlmostSuspense]

for reference the user that posted the last comment was redirected to github from ddevs because they had a valid point about bots showing in the list even if no commands are usable, this is indeed not handled by the permission system