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
You can also set a default_permission on your commands if you want them to be disabled by default when your app is added to a new guild. Setting default_permission to false will disallow anyone in a guild from using the command--even Administrators and guild owners--unless a specific overwrite is configured. It will also disable the command from being usable in DMs.
It would appear that this boolean value should be set on the DiscordCommand model after options.
The text was updated successfully, but these errors were encountered:
@ms7m Did you verify that adding default_permission=False to a DiscordCommand functions as expected with the 1.0.0b PR?
Personally, a command with default_permission=False and no other permissions set is still usable by me (the guild owner) in my tests. I'm not sure where the issue lies here.
Ah, it was an error on my part, apologies. I had old command permissions that I wasn't aware of which overwrote the default_permission. Functions as expected 👍
It would appear that this boolean value should be set on the
DiscordCommand
model afteroptions
.The text was updated successfully, but these errors were encountered: