@OffLuffy Aren’t the Lapis permissions just for simplifiying the configuration process, not being a drastically different idea of permissions? As far as I know, if you only want to have the features of e.g. PermissionsEx, you don’t need to use them and have a simple, clean and working permission setup… If I’m wrong, please correct me - I may did not fully understand the potential of those Buckets…
By the way: I’m now working with @jdf2 on this together and some things of the idea have changed drastically:
- There will be a community feature: You can just import the most-used configuration from a huge database created by everyone hosting a server.
- It will (probably only) work together with a Sponge plugin which acts as a secure REST API for the biggest permission plugins.
- It will be centralized on one website with one database and user accounts for every server admin, so everyone can and will share his setup with the community database.
- The interface will probably look completely different from what it does in the first version of jdf2’s PEXOE.
I know this may does not sound perfect for an open source-minded community to have a centralized platform to manage permissions, however this offers huge possibilities for features of all kinds instead of being just another PEx GUI.