On the few occasions I've had requests for permission plugins, it has always taken me aback a little bit. I became proficient in Java in mid-2021, and with the release of LuckPerms, becoming commonplace in mid-2020, it was strange that servers weren't utilising this option instead. But I digress.
When I make my permissions plugins, I try to model them in a similar way to LuckPerms, a plug-and-play plugin that you can dump on almost any Minecraft server jar, including Spigot, Paper and even Bungee, and have it work out of the box. It uses a web editor that allows you to make the tedious task of writing permission nodes faster, with an autocomplete system that reads the plugins in your server so you don't have to always look for permission nodes in plugin documentation. You can also set world or server specific ranks and permissions, where a prefix might display one thing on a Survival server, but show something else on the Hub. You can set permission groups and individual permissions with expiries. You can create promotion tracks to promote users in a department (i.e moderation or development) without having to remember the next rank. My permission plugins do all of this too, and slightly more.
I don't work to make my plugins better than the alternative, but what are the key differences between one of my systems and LuckPerms?
- My systems still use a web-editor, but also have options to view information in an easy to use
GUI
This is beneficial to those who want to view information without editing anything, LuckPerms uses a text-based viewer for this whilst I use a slightly nicer interface to do it.
- The editor for LuckPerms is external and single-user
When you load the LuckPerms editor, you are sent to an external website and only 1 person is intended to edit it per editor session. In mine, multiple users can edit in the same session, and if somebody pushes a change whilst someone else is editing in a different session, they'll be prompted to merge individual changes similar to Git. You also have the ability to live edit things which LuckPerms does not allow!
- Contexts are a lot more suggestive than in LuckPerms
LuckPerms uses contexts to configure where permissions should be active (i.e server, world), but it's not always clear to new users how to use them. My plugins give auto-suggestions, world & server name autocorrections, and you can query contexts in real time.
- Installations of my versions cache information for failure
If LuckPerms were to fail to connect to a database (i.e mysql, mssql, postgresql), it will stop the plugin loading. In the background when my plugins have changes pushed to them, they will automatically download a very optimised copy of the information into a sqlite on each installation in the background for if the database suddenly fails.
- Node migrator is more effective
If users are coming from a legacy permission plugin (i.e GroupManager, PermissionsEx, bPermissions), migrating permissions into LuckPerms can sometimes be an arduous task due to inconsistent note transfers, and sometimes you spend more time cleaning non-obvious inconsistencies up than if you'd have manually copied each node. My migrator is more effective and can figure out various types of config for each plugin more effectively.
- The web-editor is internal rather than external
LuckPerms offer you a way of downloading their web software onto your server to self-host the editor which is great, but because mine is built to be internal, you can customise it in any way you'd like!
- Uses a server settable locale
Whilst this was possible through the use of contexts, you could set server specific locales in the config of individual servers. By default, all created permission groups, permissions and all data related to permission groups and players was located on the 'origin' locale. If you were to change the locale to something like 'dev', then you could create an entirely new permission setup on other servers, maybe for testing or QA, then if you wanted to merge it into origin, you could!
These differences are not me putting LuckPerms down, they are relatively minor improvements for specific servers who prefer their own solutions which would be impossible for a solution like LuckPerms.
In-game GUI
This is a brief example of what one of the ingame UIs would look like outside of the web-editor. Each permission group could be associated an icon, you could enlist what groups a permission group was a part of (i.e donor or staff), add weights, prefixes and so much more! The system also supported subranks in an easy to understand way allowing you to bring in a moderator, but allow them to keep the permissions from their donor rank for example!
