Elimination of an hierarchal based permissions system

[No767]

Analyzing ModMail, the purpose of said system is to have access to some "owner-level" commands. Namely:

• ?alias
• ?block
• ?unblock

alias is eliminated as slash commands are employed, and do not allow the creation of aliased slash commands. block and unblock is effectively a role/user blacklist, which permission can be given to the admins directly. And the main commands can be given the relevant permissions or have no permissions to begin with. By eliminating this decrepit system, we gain the benefits of the modern permissions system.

Note that the help command is not needed. The slash commands provide documentation and guidance on how to use said command.

[No767]

This needs more research. Modmail purely relies on a hierachal based system, but there are no permissions checks involved. Ideally there is a system of both. Permission checks are primarily used, alongside with hierarchy checks. I'm considering copying the owner system (e.g. users have access to certain commands based on rank), but probably no owner rank as owner checks are possible.

[No767]

Having thought about this for some time, I'm looking to structure it with three different hierarchies:

1. Permission checks
2. Role Hierarchy checks (https://gist.github.com/apple502j/d1330461e7e8ad6532cb62a670d06a5a#role-hierarchy-matters)
3. Rodhaj-based internal hierarchy checks (similar to modmail)

These three will be used to check whether an command can be ran or not. Perms and role hierarchy checks will also be applied to the bot itself

[No767]

After some thinking and implementation, I am NOT doing an internal modmail-based hierarchy check at all, due to these reasons:

1. Integrating said system would introduce complexities with the current permissions system checks
2. It's insecure. Actions such as editing threads, adding channels, requires permissions. And Modmail's excuse for forcing users to invite the bot using admin perms is because of their internal hierarchy system. The hierarchy system that Modmail has basically does not protect it against discord.HTTPException errors when interacting with Discord
3. I would have to store, and bulk add users into the user_settings just to store their current permissions value. That's an extremely expensive operation to do, as there are thousands of users that need to be dealt with. This would also slow the bot down.
4. Just to spite the modmail dev team

Ultimately, permission checks with an built-in hierarchy check is what's going to be implemented. The checks are based off of R. Danny's checks, and have been modified to inject permission extras into the command so we can display what permissions are needed for what commands. If R. Danny can survive with 9,000+ servers with these checks, Rodhaj will also