Why:
Discord's permission is simple but lacks the ability for complex permission management
Feature:
Set levels a role can interact with, from being able to manage and etc. Then maybe separate paths they can manage.
Case 1:
You have a standard Minecraft server but don't want your developers to ban people and not to have your admins ban your developers.
Owner
Co-Owner
Developer
Trial developer
Admin
Trial admin
Mod
User
A setup like this on a platform like Discord you would either have to have the co-owner or owner manage the roles or give the developer access to manage administrators. It could be improved by making separate routes of a similar system.
That you set a track of Trial Developer -> Developer allowing the developer to only manage what's on their own track.
Then to have
Co-Owner -> Developer -> Trial Developer -> Admin -> Trial admin -> Mod and etc.
This aims to be much more configurable in allowing users to create custom permissions systems
Why: Discord's permission is simple but lacks the ability for complex permission management
Feature: Set levels a role can interact with, from being able to manage and etc. Then maybe separate paths they can manage.
Case 1:
You have a standard Minecraft server but don't want your developers to ban people and not to have your admins ban your developers.
A setup like this on a platform like Discord you would either have to have the co-owner or owner manage the roles or give the developer access to manage administrators. It could be improved by making separate routes of a similar system.
That you set a track of
Trial Developer -> Developerallowing the developer to only manage what's on their own track.Then to have
Co-Owner -> Developer -> Trial Developer -> Admin -> Trial admin -> Modand etc.This aims to be much more configurable in allowing users to create custom permissions systems