Permission Optimisation Suggester
About
For this, a list of all known servers needs to be compiled and send with the data if it that information is not already available. A list of all known servers should be able to be found by iterating through all permission nodes and storing them in a Set, except global. This could possibly be a yellow bulb which would show information-boxes with tips on how to clean-up the permission data.
-
If a group has the same permission for all known servers, and that all those permissions have the same world, context and expire, then suggest to replace all of them with one permission entry which has
globalas server. -
If a group has the same permission for both
globaland an another server, and both have the same world, context and expire, then suggest to remove the redundant server-specific permission as the global permission already grants that.
I am sure these rules could be expanded/optimized to fix even more of these scenarios.
Design Suggestion
I am not a designer.

Use case
For example for us this would help us removing redundant permission nodes. We have about 15 groups and after migrating from PermissionsEX we often see this:

@BrainStone Why was this closed?
Wait what?
I haven’t closed this...
I think this would be better suited as an optimisation feature for the LuckPerms plugin and not the web editor.
I think this would be better suited as an optimisation feature for the LuckPerms plugin and not the web editor.
It could be added in both, for people who don't use the web editor.
I'm open to adding something like this in the editor, but I will need some guidance on what it should check for. If anyone has any suggestions on what sort of things would be considered good for optimising permissions, please add a comment.
Give a warning about the * permission, and that it grants every permission.
https://github.com/lucko/LuckPerms/wiki/Advanced-Setup#shorthand-permissions are a thing.