LuckPerms is an advanced permissions implementation aiming to be a fast, reliable and flexible alternative to existing permission plugins. The project’s main goals are centered around high performance and a wide feature set, filling the gaps of functionality and building upon existing features found in other plugins. LuckPerms also includes an extensive API for developers, and support for a variety of Minecraft server software & data storage options.
LuckPerms is currently the only maintained and ‘working’ permissions plugin for Sponge servers.
I like seeing additional permissions systems, but does this differ in any significant way to the existing implementations?
I’m always interested in the differences rather then what’s the same between them, as I think the concept of permissions has gotten somewhat stale in the way that they are specified compared to the early days, and that there is room for innovation.
I totally agree! I noticed as I was posting this that there are a lot of alternative permission plugins popping up for Sponge, and I understand PermissionsEx has been ported too. I haven’t had a chance to look deeply into any of the alternative Sponge implementations, but my first impression was that they all seemed somewhat simplistic and lacking in features. I might be wrong though.
I made a chart comparing LuckPerms to most of the other popular implementations, although aside from PEX, they’re all Bukkit plugins. Maybe you’ll find it useful anyway, just as a comparison, so here it is: https://static.lucko.me/luckperms-compare.png
The features list above might give you a good idea too. I tried to cover most features seen in other implementations, and added a few of my own ideas, as well as a proper API and support for all of my favourite platforms (Sponge/Bukkit/Bungee).
I like this perms plugin, your commands are a little more straightforward than pex. Yet, I dont understand this WANT to get away from editing a permissions yaml. I mean even for novice server owners having to run 50 commands to get a simple group setup is inefficient. Its much easier to Define a group, set 40+ permission nodes, a prefix, suffix and inheritance inside a text file. (Thanks to notepad++ or equivalent of course!). So this hatred of taking 10 minutes to copy and paste in permission nodes vs an hour typing out all of it is kinda…well in my honest opinion, backwards thinking. I guess I myself am just a novice server owner and I always used Group Manager. And it was a cinch to set up. Once the newbie gets past the fact you need a 4 space tab, yaml isnt all that intimidating.
If you know the file format inside out, then maybe you’re right, it is quicker to type out a list of nodes in a file. However, the problem comes when you don’t know the format, you make a mistake, or want to push the same permissions across multiple servers.
File parsing errors are far far harder to diagnose with a user, than commands. At least in LuckPerms, you literally cannot make errors when setting up permissions, as it won’t let the command execute, and it will spit back an error explaining exactly what was wrong. I think you’d be lucky to get that much diagnostic when loading screwed up YAML.
Off-topic slightly, I was under the impression that Sponge wasn’t really supporting YAML? Perhaps I’m mistaken, but I’m pretty sure the de-facto for config files is .conf here? Maybe not, Idk.
Anyway, back to your point. LuckPerms actually does have support for flatfile. User, group and track data is each saved within it’s own file, in the popular json format. My advice is to generate a file for yourself, using commands, work out how the format works, and then edit the files by hand if you must.
I should also add, there is support for automatic migration from a number of existing plugins, GroupManager included. Check the wiki page for info on that.
Thanks for hearing me out. And you are right sponge is using hocon. Snake yaml would always spit out the line in the console/log stating what line in the group manager config was not formated properly. I think that there should just be a template group, world and user in the flat file for those who prefer flat file but are not familiar with the hocon format.
There will be files there by default. A default group is made when the server first starts, and new user files are made whenever a new player joins the server. You should be able to work out the format just by looking at those files, or using the commands if you’re unsure about how to setup inheritances, per server/world permissions, prefixes/suffixes, etc.
LuckPerms is lacking context implementation which PEX supports. Without this feature, many sponge plugins such as GriefPrevention will not be able to work with your plugin as it is a crucial part of Sponge’s Permission’s API. I would suggest implementing it =). I also see no support for options.
@Beauseant Because a user with that UUID hasn’t joined the server since you installed the plugin.
@blood Yeah, it doesn’t currently implement PermissionService, just relies on the default Sponge backed one. (mentioned in caveat #1 in the original post) I wasn’t aware that this was an issue, though, so thank you for letting me know.
I intend to implement it soon, and actually did try to do it initially, but found the entire thing to be incredibly complicated. I’m sure it makes perfect sense to you, but as someone reading the API for the first time, it was pretty hard to understand. The Sponge Docs article on permissions is also empty, which made it even harder, as I was just reading javadocs and source code, without any real explanation of what the purpose of the entire system is. I even spent a good hour or so reading over the PEX 2.0 source code, to see how it was implemented, and I couldn’t make much sense of that either.
I plan to work on it eventually. For now, this plugin serves as a way to serve the same permissions to a Bungee proxy and a network of Sponge servers, for those looking for that sort of functionality.
Edit: Actually no, I take that back. The PermissionService made absolute sense, the part that really confused me was the whole Context system. Are plugins forced to add an implementation for all of the static contexts in the Context class? The JavaDocs for Contexts in general is really brief. Anyway, I’ll take another look.
Strange, i’ve logged in multiple times but it hasn’t added me yet. When does it generate my UUID? At login?
Also, can you explain me why i get this error? I’m really not into Forge (sponge) yet, so sorry if i’m asking a lot of questions http://pastebin.com/ghhPGw4L
Yep, but you shouldn’t have to do that. I was under the impression that it was always present. (At least it has been in my testing) Meaning I’m not handling MySQL correctly. I’d appreciate if you tell me which version it is, so I can attempt to fix it for other users.
Also, i want to suggest a feature. I’ve run into problems multiple times with giving people OP just to let them use command blocks. I would give them OP, and then forget about it after a while; without taking away OP rights. I’ve been used to a feature with a custon Spigot plugin to de-op players automaticly if they join. So they need to receive it from someone who can supervise the command block usage; just because they can do things with OP rights which are pretty devestating.
Could you let there be a config option in which we could automaticly de-op players on join? I think it would be an awesome feature, not only for me but for other users as well!