You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using luckperms but I fing myself scrolling from top to bottom multiple times in order to find the permission node that I need. While a search bar might help with this issue, I don't believe in anyone knowing more than X number of permission nodes. That's why we need "views" inside the LP editor.
One way to improve the usabaility of the editor is to have a button to cycle between these three options, which mainly consist in alternating a new way of grouping permission nodes based:
Disabled: No grouping is done, this is what we currently have in the editor.
Root Grouping: LP editor will try to group every permission node based on the root permision node. For instance: luckperms.a luckperms.b luckperms.c luckperms.d would be grouped together inside a "luckperms" category. This feature will declutter the list of permissions by a ton.
Sub-node Grouping: Since grouping exclusively by the root node might not be enough for some plugins which have many different perm nodes that share atleast two nodes, for example: luckperms.user.a luckperms.user.b luckperms.user.c luckperms.user.d. It would be great to try to group things up even further. But since there's no simple way of knowing how much is enough grouping for a determined plugin, some more options might be needed. Now here's my take on how to fix this inconvenience: Once you are at this grouping option, a little scrollbar would appear somewhere near the button. It enables the user to specify how much grouping does he want by simply scrolling the bar from 1(root permission) to All(The editor will try to group everything as deep as possible.) where in between does two values are integers. There's one inconvecience added to this. How do we know what values are between "1" and "all", the plugin would need to scan for the deepest permission node? And then have that value in cache and on startup scan again?
Just to make sure, this suggestion does not involve any modifications of the permission system. It's just a visual enhancement for those who have a huge list of permissions.
The text was updated successfully, but these errors were encountered:
I've been using luckperms but I fing myself scrolling from top to bottom multiple times in order to find the permission node that I need. While a search bar might help with this issue, I don't believe in anyone knowing more than X number of permission nodes. That's why we need "views" inside the LP editor.
One way to improve the usabaility of the editor is to have a button to cycle between these three options, which mainly consist in alternating a new way of grouping permission nodes based:
Just to make sure, this suggestion does not involve any modifications of the permission system. It's just a visual enhancement for those who have a huge list of permissions.
The text was updated successfully, but these errors were encountered: