New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Re-definition of permission system #4

Closed

zneix opened this issue Dec 16, 2019 · 1 comment

Projects

MongoDB connection features

Owner

zneix commented Dec 16, 2019

review of current superusers (make possible changes)
guild_perm should use boolean OR instead of AND
per-guild permission levels (that includes defining guild bot admin and guild bot mod role with ability to change that with config command)
re-defiition of global bot admin/mod permissions

zneix created this issue from a note in MongoDB connection features (Being Implemented)

Owner Author

zneix commented Dec 16, 2019

TBD
Done
Only guild mod role is defined for now, might implement admin later. Config command supports changes.
Command permission level is now an array at 100% of times. That is presented in a following format:

Global permissions requirement (or false if not required)
Guild-based role requirements (or false if not required), ADMINISTRATOR permission can override those.
Optional Discord permissions to check (like KICK_MEMBERS in kick command)

zneix closed this as completed

Repository owner locked as resolved and limited conversation to collaborators

zneix moved this from Being Implemented to Implemented features in MongoDB connection features

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.