Sub command Permissions V2

[Luc1412]

As currently planed, subcommands won't be supported with the new permissions system. This is due to sub commands having no individual ID.

This is really unfortunate as there are many use cases for sub commands permissions. eG.

/example start - Should be public
/example settings - should be Moderator only

[Rapptz]

Something simple like:

/tag get for anyone to be able to retrieve a tag and /tag create being limited to certain people or roles is also impossible due to this system constraint.

[menix1337]

Quite a while without answers.

I really hope this gets looked into, unless i overlooked something and its already fixed?
being able to moderate subcommand groups would be so handy

[Fortex365]

Hey,

just use in your subcommand this:

if not ctx.author.guild_permissions.manage_messages:
    await ctx.send("You are missing Manage Messages permission(s) to run this command.", ephemeral=True)
    return

as a temp solution. Slash commands and Hybrid commands handles it well, using Hybrid Group gotta use it on your own

[menix1337]

Hey,

just use in your subcommand this:

if not ctx.author.guild_permissions.manage_messages:
    await ctx.send("You are missing Manage Messages permission(s) to run this command.", ephemeral=True)
    return

as a temp solution. Slash commands and Hybrid commands handles it well, using Hybrid Group gotta use it on your own

Aye, i ended up doing this here - just for the sub commands where i want stuff locked off on.

const requiredRoles = ['Head Admin', 'Tech Admin', 'Senior Admin']

const roles = interaction.member.roles as GuildMemberRoleManager

if (!roles.cache.some((role) => requiredRoles.includes(role.name))) return; 

Would just be nicer in a overall way for the Discord Moderators etc to be able to adjust things on their end, but i guess until Discord catches up we still gotta do some stuff manually for Sub Commands! :D

[ManHatos]

bump, this is very frustrating