Skip to content
This repository has been archived by the owner on Nov 25, 2022. It is now read-only.

Extended permissions system #48

Open
5 tasks
zzzowoey opened this issue Feb 4, 2020 · 0 comments
Open
5 tasks

Extended permissions system #48

zzzowoey opened this issue Feb 4, 2020 · 0 comments
Labels
feature New feature or request planned/1.x

Comments

@zzzowoey
Copy link
Member

zzzowoey commented Feb 4, 2020

Problem

Using Discord's permissions alone is really confusing from the end user's standpoint and doesn't offer enough fine-grained control over what the bot and/or guild members can do. I'd like to propose a new permissions system, and will be developing the idea more over time.

First steps and core ideas

These aren't necessarily in any sort of order.

  • Completely do away with the use of Discord permissions in module declarations.
    I think we can probably find a way to deal with these upstream, but I haven't experimented enough with how Discord4J handles "insufficient permissions" errors.
  • Offer a small set of clearly-named "access levels" that gradually offer access to more commands as you "climb the ladder"
  • Implement a way to attach these access levels to certain roles and/or groups of roles
  • Provide a clear, clutter-free interface for managing access levels and delegating commands
  • Develop a system for storing these settings to the persistence layer
@zzzowoey zzzowoey changed the title [1.x] [Feature] Extended permissions system Extended permissions system Jun 5, 2020
@zzzowoey zzzowoey added feature New feature or request planned/1.x labels Jun 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature New feature or request planned/1.x
Projects
None yet
Development

No branches or pull requests

1 participant