docs: Interaction Service Perms-v2 docs (#2263)
* add perms v2 docs * add perms v2 docs
This commit is contained in:
@@ -158,6 +158,14 @@ Interaction service complex parameter constructors are prioritized in the follow
|
|||||||
2. Constuctor tagged with `[ComplexParameterCtor]`.
|
2. Constuctor tagged with `[ComplexParameterCtor]`.
|
||||||
3. Type's only public constuctor.
|
3. Type's only public constuctor.
|
||||||
|
|
||||||
|
#### DM Permissions
|
||||||
|
|
||||||
|
You can use the [EnabledInDmAttribute] to configure whether a globally-scoped top level command should be enabled in Dms or not. Only works on top level commands.
|
||||||
|
|
||||||
|
#### Default Member Permissions
|
||||||
|
|
||||||
|
[DefaultMemberPermissionsAttribute] can be used when creating a command to set the permissions a user must have to use the command. Permission overwrites can be configured from the Integrations page of Guild Settings. [DefaultMemberPermissionsAttribute] cumulatively propagates down the class hierarchy until it reaches a top level command. This attribute can be only used on top level commands and will not work on commands that are nested in command groups.
|
||||||
|
|
||||||
## User Commands
|
## User Commands
|
||||||
|
|
||||||
A valid User Command must have the following structure:
|
A valid User Command must have the following structure:
|
||||||
|
|||||||
Reference in New Issue
Block a user