You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I double checked the docs and couldn't find any useful information.
Verify Issue Source
I verified the issue was caused by Discord.Net.
Check your intents
I double checked that I have the required intents.
Description
When [DefaultMemberPermissions(0)] is used on a single command library output its a null and not as 0.
Expected outcome is 0 as default permissions what should result in Administrator Only on the command
When [DefaultMemberPermissions(0)] is used with a group command then this behaviour works as it should.
And this results on Discord as Adminstrator Only Command
Version
3.16.0
Working Version
No response
Logs
-
Sample
No response
Packages
Environment
The text was updated successfully, but these errors were encountered:
BlackDevil115
changed the title
[Bug]:
[Bug]: DefaultMemberPermissions(0) not handled correnct on a single command
Sep 17, 2024
BlackDevil115
changed the title
[Bug]: DefaultMemberPermissions(0) not handled correnct on a single command
[Bug]: DefaultMemberPermissions(0) not handled correct on a single command
Sep 17, 2024
Hey!
While that is technically correct, changing it at this point would introduce a breaking change;
We might change it in v4, but until then you could set the permission to Administrator
Check The Docs
Verify Issue Source
Check your intents
Description
When [DefaultMemberPermissions(0)] is used on a single command library output its a null and not as 0.
Expected outcome is 0 as default permissions what should result in Administrator Only on the command
..\src\Discord.Net.Interactions\Utilities\ApplicationCommandRestUtil.cs
When [DefaultMemberPermissions(0)] is used with a group command then this behaviour works as it should.
And this results on Discord as Adminstrator Only Command
Version
3.16.0
Working Version
No response
Logs
Sample
No response
Packages
Environment
The text was updated successfully, but these errors were encountered: