Subcommands Should Have Default Member Permissions Too #7813
Unanswered
Neodevils
asked this question in
API Feature Requests & Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
As an interaction command developer, I’ve noticed a limitation: the default member permission property currently only applies to top-level commands, not to subcommands or subcommand groups.
This creates unnecessary friction for common use cases. For example:
/tag
command with subcommands:/tag create
→ should be restricted to server managers/tag use
→ should be available to everyoneCurrently, developers must manually handle permission checks inside each subcommand’s logic. If default member permissions could be applied to subcommands as well, it would:
Is this something that could be added in the API? It would greatly improve the developer experience for multi-level commands.
Beta Was this translation helpful? Give feedback.
All reactions