LuckPerms

Luck · February 1, 2017, 6:58pm

This is a discussion topic for the Ore project, LuckPerms. View the full project on Ore for downloads and more information.

LuckPerms is a permissions plugin for Minecraft servers. It allows server admins to control what features players can use by creating groups and assigning permissions.

It is:

fast - written with performance and scalability in mind.
reliable - trusted by thousands of server admins, and the largest of server networks.
easy to use - setup permissions using commands, directly in config files, or using the web editor.
flexible - supports a variety of data storage options, and works on lots of different server types.
extensive - a plethora of customization options and settings which can be changed to suit your server.
free - available for download and usage at no cost, and permissively licensed so it can remain free forever.

LuckPerms is currently the only maintained and ‘working’ permissions plugin for Sponge servers.

For more information, see the wiki article on Why LuckPerms?

Useful Links

The latest downloads & other useful links can be found on the project homepage at luckperms.net.

The plugin has extensive documentation available on the wiki. Please use the resources there before coming to us directly for support.

Support for the plugin is provided on Discord. If you have a question which cannot be answered by reading the wiki, the best place to ask it is there.

If you would like to report a bug, please open a ticket on GitHub.

External connections

In order to deliver it’s functionality, LuckPerms will under some circumstances make connections with and communicate with external services outside of the local server.

The nature of these connections are detailed on this wiki page.

Luck · February 3, 2017, 7:26pm

/lp group admin permission set * true

You’ll be told by most people that using wildcards in this manner is bad practice, but it’s exactly the same as PEX’s defaults system.

Linoko · February 16, 2017, 11:04am

I have a few general questions regarding tracks. On my server I wish to have several tracks, but some that only specific groups can promote/demote along.

For instance: I only want my server to be able to promote/demote along the track following donations (iron->gold->diamond), but I want my moderators to be able to help promoting/demoting on the general rank track on the server (visiting->user->mod->admin).

To the question: Is there any way to handle permissions regarding promotions/demotions on mutliple tracks? In addition, is there any way to prevent self-promotion via permissions (mod promotes himself to admin)?
I was thinking of something like:

“name”: “mod”,
“perms”: {
“luckperms.user.promote.rank”: true,
“luckperms.user.promote.donations”: false,
“luckperms.user.promote.rank.admin”: false,
}

Luck · February 25, 2017, 11:22pm

Apologies for the late reply, your message must’ve slipped past me.

Currently, no, this is not possible, however, it has been addressed by this issue, and will hopefully be added soon.

github.com/lucko/LuckPerms

Selective command permissions

opened 10:38PM - 08 Feb 17 UTC

closed 11:43AM - 07 Jul 17 UTC

lucko

type: suggestion

Pretty low priority, would be cool though. ## Some examples ### `/lp user <u…ser> promote <track>` Currently checks for luckperms.user.promote Should be changed to check: * luckperms.user.promote.\<track\>.\<group promoting to\> (if false return, if true allow, if undef continue) * luckperms.user.promote.\<track\> (if false return, if true allow, if undef continue) * luckperms.user.promote (if true, allow, otherwise deny) Should be the same for demote. ### `/lp user <user> parent add <group>` Currently checks for luckperms.user.parent.add Should be changed to check: * luckperms.user.parent.add.\<group\> (if false return, if true allow, if undef continue) * luckperms.user.parent.add (if true, allow, otherwise deny) Should be the same for permission equivalents. ## How to determine whether players can actually use the command I guess this should be achieved through parsing the command string directly. Instead of doing the check at execution, it will be done ahead of time.

Luck · March 7, 2017, 10:12pm