search

PEXPlugins / PermissionsEx

A powerful permissions plugin for Minecraft
https://permissionsex.stellardrift.ca
Apache License 2.0
481 stars 297 forks source link

Will PEX continue to be updated? #696

Closed Jeronimo95 closed 11 years ago

Jeronimo95 commented 11 years ago

So I've here a lot of things about PEX recently, like how its not maintained or is outdated. People seem to think PEX is bad... I'm am looking for a way to organise all the permissions over my multiple servers into one easy to manage system. My thinking was to use SQL and build a web interface to manage my servers, as far as I can see the only permissions plugin to support SQL is PEX.

My question is: Is PEX going to be maintained? I like PEX, and I've used it for a wile, but I don't want to put the effort into building an entire system for my servers if it will break in a few months.

Thanks, Jeremy

Bubelbub commented 11 years ago

It is open source. You could develope it :D

Whats your Feature wishes?

Jeronimo95 commented 11 years ago

My feature wish is to have a permissions plugin that is going to be maintained. Something that will stay working for the forcible future.

I would develop it myself, but I don't know a lot about Java. If the current developers have 0 intent to maintain it, I might learn some more Java and -try- and maintain it.

SimSonic commented 11 years ago

Good day! I want to intruduce some my ideas about pex's future.

  1. Not to inject own code into Bukkit but work with Bukkit's system.
  2. Add prefixes to database colums.
  3. Add column "level" in "permissions_inheritance". This should allow player to have permissions to do something wneh he reaches high levels. Example use: type = 0, child = default, parent = highlevelplayers, world = null, level = 40. It can help to create very interesting roleplay servers with "native" support of races (groups), ladders and levelling.
  4. And new essence (column) like "server" in addition to "world". Plugin can get it from server.properties. Currently I have 4 servers successfully working from single pex database and I had to make different world names. I't not a big problem but can be good feature.

codefail, I know Java badly, but I'm interested in its development, and can try to help you.

Jeronimo95 commented 11 years ago

HI SimSonic, sorry for the late reply, As I said - If the current developers have 0 intent to maintain it, I'd be happy to help.

As per your Ideas:

  1. I haven't looked into pex's code much, but this sounds like it could be good.
  2. Why would you need to prefix database columns?
  3. I'm not sure I understand, could you elaborate?
  4. Sounds like a great feature for multi server communities.
SimSonic commented 11 years ago

HI SimSonic, sorry for the late reply,

Not so late =)

Why would you need to prefix database columns?

In my opinion it should be able to every good plugin.

Add column "level" in "permissions_inheritance". I'm not sure I understand, could you elaborate?

Ok. I want to build roleplay server. For example, I can have such groups: default, citizen, senior, leader. The groups are in single ladder, so player can be moved up/down by promotion/demotion. In parallel with this I want players to be devided into low-level, mid-level and hi-level groups. Leveling groups will give access to some extra crafting receipts, abilities and etc., figuratively speaking. So in the config it should looks like this: Group default: inherit low-level on player's level 10. Group default: inherit mid-level on player's level 30. Group default: inherit hi-level on player's level 80. Group citizen: inherit group default and have higher rank. Group senior: inherit group citizen and have higher rank. Group leader: inherit group senior and have higher rank. Level condition column can be realized both for permissions and permissions_inheritance tables.

Sorry for my bad english, please.

Sounds like a great feature for multi server communities.

A minute ago I came up with idea ​​continuation. This will not require new columns. Just change values for world columns in database like this: 'world@serverId' or more correctly: NULL or empty string or asterisk () — everywhere. 'worldname' in worlds with this name. '@serverId' or '@serverId' on server with specific serverId value. 'worldname@serverId' in specific world on specific server.

New feature.

  1. Option for regular timed reloading in config. Now we should use something like websend to reload pex after adding user to premium group by web scripts. Alternative is waiting for restart which can be scheduled for 8 up to 24 hours.
zml2008 commented 11 years ago

This issue is no longer relevant with the upcoming PermissionsEx 2.0. See this forum post for more information.