Permissions plugin (Ideas?)

[SubSide]

So I'm thinking about making my own permissions plugin (like GroupManager and PEX),
which I might make open-source on my git.

now my question to you guys is:
What would you like to have in the permission system that the other plugins don't have?

 

[Skionz]

IMO, no point in reinventing the wheel. Other plugins already have pretty much every realistic feature unless you want to implement some random permission mini-games into yours.

 

[Lethal]

IMO, no point in reinventing the wheel. Other plugins already have pretty much every realistic feature unless you want to implement some random permission mini-games into yours.

Or make them easier to work with and fix some flaws.

 

[Skionz]

Or make them easier to work with and fix some flaws.

It would be better just to use vault and write an inventory GUI, or such instead of having to configure each plugin with commands, or a file instead of writing an entirely new permissions plugin.

 

[K3Feedz]

So I'm thinking about making my own permissions plugin (like GroupManager and PEX),
which I might make open-source on my git.

now my question to you guys is:
What would you like to have in the permission system that the other plugins don't have?

Global and Local ranks
Global - MySQL
Locals - Local server

 

[Twistaar_]

Make it simple to use, but with some advanced features. Like Pex, how it's /pex user, /pex group etc.

 

[K3Feedz]

All Inventory GUi controlled

That'll be dumb, how would you use it through console.

 

[JungleSociety]

Perhaps create a database with some of the most popular plugins and their commands paired with their permissions. So a player would be able to easily setup permissions by providing the command itself instead of the permission. For example, most servers use essentials, so it would be cool if you could create a database of all or most of the essentials commands with their permissions, so then you could access the data base and retrieve the permission that correlates to the command along with the plugin name itself. An example command would be /permissions group group1 add /fly. It would then access the database and try to find a command called '/fly'. If it finds it, then the plugin will check to see if the server has the plugin that the database uses for the permission, if it does then it will simply add the permission that the database contains. Here is an example of what would happen:

You have a database that is made specifically for this plugin (maybe just a YAML file):

/fly:
  plugin: Essentials
  permission: essentials.fly
/OTHERCOMMAND:
  plugin: PLUGIN
  permissions; ITS PERMISSION

then the plugin could access this file when the command to add a permission is executed. So if a player did the following:
/perm group group1 addcmd /fly

Then the plugin would go to this file and try to access the /fly section, if it finds it, it should see if the server has Essentials, if it does, then it should add the permission essentials.fly to group1. I just kind of came up with this on the top of my head, and I thought it would make adding permissions a bit easier for common plugins. Of course this would have problems with aliases, other plugins having the same command, etc. This might not even work well and you probably have no clue what I'm trying to describe .

 

[SubSide]

Perhaps create a database with some of the most popular plugins and their commands paired with their permissions. So a player would be able to easily setup permissions by providing the command itself instead of the permission. For example, most servers use essentials, so it would be cool if you could create a database of all or most of the essentials commands with their permissions, so then you could access the data base and retrieve the permission that correlates to the command along with the plugin name itself. An example command would be /permissions group group1 add /fly. It would then access the database and try to find a command called '/fly'. If it finds it, then the plugin will check to see if the server has the plugin that the database uses for the permission, if it does then it will simply add the permission that the database contains. Here is an example of what would happen:

You have a database that is made specifically for this plugin (maybe just a YAML file):

/fly:
  plugin: Essentials
  permission: essentials.fly
/OTHERCOMMAND:
  plugin: PLUGIN
  permissions; ITS PERMISSION

then the plugin could access this file when the command to add a permission is executed. So if a player did the following:
/perm group group1 addcmd /fly

Then the plugin would go to this file and try to access the /fly section, if it finds it, it should see if the server has Essentials, if it does, then it should add the permission essentials.fly to group1. I just kind of came up with this on the top of my head, and I thought it would make adding permissions a bit easier for common plugins. Of course this would have problems with aliases, other plugins having the same command, etc. This might not even work well and you probably have no clue what I'm trying to describe .

Yeah, this is something I was thinking of, just adding the command for the permission.
It would be difficult though, for commands that accept multiple permissions, for example worldedits tool permissions,
the arguments /tool tree and /tool repl have different permissions,
/tool tree has worldedit.tool.tree, and /tool repl has worldedit.tool.replacer

Or how about a ban plugin with a permission to ban a player that is offline? like essentials has essentials.ban.offline or for exempting the player from bans: essentials.ban.exempt
It would be pretty difficult to implement such a thing. Yes I could do like /perm add ban offline, and add ban exempt,
but it would be pretty difficult to add a very easy to use system for that, as I don't want it to become a guessing game.

^^

 

[JungleSociety]

Yeah, this is something I was thinking of, just adding the command for the permission.
It would be difficult though, for commands that accept multiple permissions, for example worldedits tool permissions,
the arguments /tool tree and /tool repl have different permissions,
/tool tree has worldedit.tool.tree, and /tool repl has worldedit.tool.replacer

Or how about a ban plugin with a permission to ban a player that is offline? like essentials has essentials.ban.offline or for exempting the player from bans: essentials.ban.exempt
It would be pretty difficult to implement such a thing. Yes I could do like /perm add ban offline, and add ban exempt,
but it would be pretty difficult to add a very easy to use system for that, as I don't want it to become a guessing game.

^^

Good point, as I said I just came up with it. And obviously this probably wouldn't work out Just a thought.

 

[SubSide]

Good point, as I said I just came up with it. And obviously this probably wouldn't work out Just a thought.

Yeah, I am a person that over-think things, if I have an idea, or if I'm thinking of something, I over think it, and already come up with how I would implement it, which issues it could cause, which problems will I encounter making it.
Could be an advantage and disadvantage sometimes.

Really helpful with making plugins though, as I am most of the time very fast if it comes to finding exploits and such

 

[SoldierAlex]

I think this would be awesome and you could maybe make it so that it's easy for someone to set it up.
Idea-
/permgroup create (permgroup name)
/permgroup give (permission)
This is something that would help people easily setup a server without having to know too much stuff. This is just an idea and I probably don't know what I'm talking about.

 

[Potrock]

I think this would be awesome and you could maybe make it so that it's easy for someone to set it up.
Idea-
/permgroup create (permgroup name)
/permgroup give (permission)
This is something that would help people easily setup a server without having to know too much stuff. This is just an idea and I probably don't know what I'm talking about.

Group Manager is about as simplistic as it gets

 

[SoldierAlex]

Group Manager is about as simplistic as it gets

Idk I don't use it...

 

[SubSide]

What I also could do is use it as an "addon" on to existing plugins, like just a plugin build on top, so you are able to do those simple commands.

 

[Satelliting]

Group Manager is about as simplistic as it gets

Idk.... PEX is pretty darn simple.

 

[TechBanana]

Perhaps an optional (able to enable/disable) /rankup system. And as SoldierAlex said, the permissions group would be cool.
For example if the plugin is called SSPerm:
/ssperm pgcreate [name]
/sspern pgadd [name] [permission]
Or
/ssperm pgadd [name] [perm],[perm2],[etc]
Then to apply it to a group:
/ssperm gadd [group] ssperm.pg.[name]

 

[SubSide]

I was thinking about a level system that was very populair on Wolfenstein: Enemy Territory (a game I play(ed) a lot)

Basically, you could set like the permissions per command, per level, and then you could do like /setlevel [player] level
and the higher the level, the better, and people with a lower level wouldn't be able to kick/ban/mute higher people.

It's a pretty cool concept which I think would be really cool to implement. =)