Skip to content
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.

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

(Suggestion) Permission cog | Per user settings and something like #server. #49

Open
Salty-Panda opened this issue Mar 15, 2017 · 2 comments

Comments

@Salty-Panda
Copy link

Salty-Panda commented Mar 15, 2017

I appreciate permissions system in Rem bot. Simple, with priority order. Options like:
blacklist entire server, then whitelist two channels, then blacklist a Moderator rank in those channels, but whitelist user there. (user>role>channel>server order), one can use * to include all commands/modules.
Or option to lock module but unlock one command.

So:
Lock system here is useful, but if you lock cog and unlock command (both globally), command still is locked. That system is hard to manage. Maybe instead of locking cog make it to work as loop of locking commands?
Same with other. There should be a priority order.
If user has permission do it, else if any of users roles has permission do it, else if channel has perm. do it, else if server has perm. do it, else don't.

Do you plan to add subcomands to black/whitelist, such as channel/cog/command?

PS. Yes, my English isn't clear to understand, sorry.

@tekulvw
Copy link
Owner

tekulvw commented Jun 14, 2017

Not going to be available in V2, likely will add to V3 implementation of permissions but that's a long way down the road and the featureset isn't set in stone yet.

@tekulvw
Copy link
Owner

tekulvw commented Jun 14, 2017

And I'm gonna loop #43 into here so I can close it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants