Inactive [ADMN/DEV] Permissions v2.7.4 (Phoenix) - DISCONTINUED! 3.0 has a new home!

Permissions 2.7.4 (Phoenix) - Now with AntiBuild built in!
Download:
Latest Stable: Full Zip | Jar Only
Latest Dev Build: Full Zip | Jar Only
Previous Versions: 2.7.3 (JAR) | 2.7.2 (JAR) | 2.7.1 (JAR) | 2.7 (JAR) | 2.6 (JAR) | 2.5.5 (JAR) | 2.5.4 (JAR) | 2.5.3 (JAR) | 2.5.2 (JAR) | 2.5.1 (JAR) | 2.5 (JAR) | 2.4 (JAR) | 2.3 (JAR) | 2.2 (JAR)

Source - Wiki - Bug Tracker​

Plugin Authors: How to hook into Permissions​

Permissions 2.x is being discontinued! 3.0 can be found HERE!!!


I am discontinuing Permissions 2.x and leaving the project. Permissions is not going away though! Since 2.6 I have been working closely with another developer and added them to the team. For the past several version they have not only been assisting with 2.x but also doing a lot of the development of much anticipated 3.x. rcjrrjcr will be taking over as lead developer of Permissions from 3.x forward. I have full faith in them and after working closely with them on the development on the last few version and the next major version I feel that I am leaving this project in more than capable hands. I put way to much work into this project to just leave it with anyone, and this is one of the few programs that I am incredibly proud of.

Many people will probably wonder why I am leaving again after taking over the project just a few months ago. I could quote drama and headaches, of which there were quite a few with this project. Unfortunately real life happens. Many people already know that I have been having medical issues here lately. Unfortunately while they have gotten better, they have not gone away. This coupled with other real life commitments, going to school full time, and starting up my own company, I am currently in the process of being laid off from work. At this point I have so much stuff going on in my life and am being pulled in so many directions that I am not able to get any work done on anything. This has lead to me missing commitments and letting people down on multiple things.

Permissions is also a very high maintenance plugin that requires a lot of attention and time. Right now I am not able to devote that time and do not feel it is fair for me to try to continue to be the lead developer on it. I had originally thought that adding other members to the team would be helpful, but unfortunately this just lead to frustration for them and myself as I just was not able to commit to the project enough. Hence, 3.0 has been rewritten almost exclusively by rcjrrjcr with minimal contributions by myself.

At this point I will be stepping away from the project to focus more on real life and to try to free up some time for other projects and to work with more individual like the wonderful HeroCraft Coding team to fulfill some commitments that I made to them a long time ago and sadly did not come through on. I feel that this is the best for all involved, both myself and the other Permissions developers, as well as the community who deserve someone who can contribute more time and attention to them and supporting them. I do not want to see Permissions end up like many other plugins with an absentee programmer and just slowly wasting away from a great plugin with a lot of potential to a headache with no support.

I will still be active in the community, just not as much as not in the same way. I'm sure my server will be more than happy to have their head admin back and active again as well.

Thank you and happy gaming.




Changelog

• 2.7.4
  • Added overload of has() and permissions() for plugin devs
• 2.7.3
  • Fixed negate node add/remove bug.
• 2.7.2
  • Fix for small subtle bug introduced in last minor version.
• 2.7.1
  • Commit by DThielke to fix several bugs with programmatic modifications of user permissions.
• 2.7
  • Further commits by rcjrrjcr
    • Removed negatedNode checks
    • Temp fix for NULL issue
    • WorldConfigurationModification to save only modified configs
    • Fix for cache problems
• 2.6
  • Pulled in commits by rcjrrjcr
  • Fixed versioning. Last version should have technically been 2.6
  • Fixed invalid config file being written
  • Fixed erroneous conversion message.
• 2.5.5
  • Updated to be compliant with CB600+
  • Further Maven Integration and Autobuilding
  • Better handling of configuration file errors.
    • If you do not have a world config file for the default world at startup it will now look for config.yml
    • If it cannot find that it will look for world.yml instead in case you named it that when that is not what is in level-name:
    • It will rewrite the config file to be the proper name. At this time it does not delete the old one though.
  • Removed defunct public abstract calls. If your not using the right one by now you should be shot anyway.
• 2.5.4
  • • Added Command aliases for perms and pr
    • Changed the way directories are handled.
    • Stopped it from creating an empty <world>.yml file in base directory
    • Moved project to using Maven.
• 2.5.3
  • Change from File.pathSeparator to File.separator to fix multiworld perms
• 2.5.2
  • Added more instructions to the included config file within the plugin
  • Added a check that will use the default world permissions if a world specific config file cannot be found.
  • Added a function to get only the group that a player is assigned to without checking for group inheritance.
  • Added a change to colorize() to fix it hopefully not adding an extra unneeded ascii character and thus creating a linebreak/color switch issue
  • Removed permissions.info as it was not needed and was a artifact of testing I was doing.
• 2.5.1
  • Fixed a bug that could cause a group to be returned as null for getGroups()
• 2.5
  • Added in AntiBuild functionality to Permissions
  • Minor code tweaks
  • Added getGroups(world, player) to PermissionHandler so that plugins can call it to get all of a users groups
  • Fixed the inability to use the permissions -reload all command from within the console. I still need to do some more work on this as it doesn't seem to like to accept anything other than all from console.
• 2.4
  • Refactored namespaces to keep in line with Java & Bukkit policy
    • This was cancelled as it ended up being not needed
  • Fixed setupPermissions()

• 2.3
  • Undid removal of some code that I had overzealously purged during cleanup
  • Merged in last of Nijikokun's changes
  • Re-ordered the main class to attempt to fix the problems with Plugin API
• 2.2
  • Developer change
  • Fixed reloading of configuration files
  • Moved commands to registering with plugin.yml
  • Commands now use onCommand instead of onPlayerCommand
  • Command is now /permissions instead of /pr

[/SPOILER]

 

I can't seem to get the Prefix/Suffix's working on any player.

Code:

    Admins:
        default: false
        info:
            prefix: ''
            suffix: '-GOD'
            build: true
        inheritance:
        permissions:
            - '*'

Is my Admins group, but -GOD won't show up after my name, or before if I put it in prefix...no errors or anything in the console either.

 

I don't think Permissions uses the prefix and suffix; it just provides them for other plugins to check.

 

Ah I see, I should read the config more closely

 

Reposting. I'm not at home right now, so I can't test to see if anything is particularly wrong aside from the throwing of errors, but regardless, I'd like to know if a fix for #561+ is in the works, for when the Recommended Build moves up.

 

Operators (ops.txt) can use any permission they want, regardless of this plugin on my server for some reason :\
Is there a way to fix this?
I'm running v2.5.4

 

Hello, i would like to ask for some help.
I want a rank to be able to: Claim areas on WorldGuard and to be able to use the basic command /set time and /tp how can this be done? how would the text look like?

Atm it looks like this
Builder:
default: false
info:
prefix: ''
suffix: ''
build: true
inheritance:
- Default
permissions:
- 'worldedit.selection'
- '/region'
- '/regionclaim'
- '/time set'
- '/tp'

But it doesn't work, how to i proceed to make it work?

Thanks in advance for any tips!

 

You have the same problem as Killgoblen

Your config file should look like this. This should make your plugins work.
I don't know how much that will fix, but it'll do.
What you did, was you needed an extra 4 spaces for all lines after and including the "Groups:" section.

You'll want it looking like this:

Code:

        Builder:
            default: false
            info:
                prefix: ''
                suffix: ''
                build: true
           inheritance:
               - Default
           permissions:
               - 'worldedit.selection'
               - '/region'
               - '/regionclaim'
               - '/time set'
               - '/tp'

Though i think your nodes a little funky- I don't think it accepts commands set up as slashes to work.

Edit: That is, I'm pretty sure they have to be look like "pluginname.command" not "/command".

Edit2:
For the /Time and /tp command, you'll want to add these:

Code:

            - 'general.time'
            - 'general.teleport'

I think, at least.

Post your config file, please.

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

Code:

plugin:
    permissions:
        system: default
        copies: null
groups:
    NotAllowedToBuild:
        default: true
        info:
            prefix: null
            suffix: null
            build: false
        inheritance: null
        permissions:
        - general.spawn
        - iConomy.payment
        - iConomy.list
        - JumpBlock.Use
        - JumpBlock.Create
    RegularUser:
        default: false
        info:
            prefix: null
            suffix: null
            build: true
        inheritance:
        - NotAllowedToBuild
        permissions:
        - mywarp.warp.basic.warp
        - mywarp.warp.basic.createprivate
        - mywarp.warp.basic.createpublic
        - mywarp.warp.basic.delete
        - mywarp.warp.sign.warp
        - mywarp.warp.sign.create
        - mywarp.warp.basic.list
        - general.time
        - general.teleport
        - general.teleport.here
        - general.player-info
    Moderator:
        default: false
        info:
            prefix: null
            suffix: null
            build: true
        inheritance:
        - NotAllowedToBuild
        - RegularUser
        permissions:
        - general.time
    Admin:
        default: false
        info:
            prefix: null
            suffix: null
            build: true
        inheritance: null
        permissions:
        - '*'
        - epiczones.test1.build
users:
    DarkGrave:
        group: Admin
        permissions: null
    v3nd377a:
        group: Admin
        permissions: null
    ccxvi:
        group: Admin
        permissions: null
    whatsherface:
        group: Admin
    Mindstormy:
        group: RegularUser
    alanosaur:
        group: RegularUser
    Regardlessness:
        group: RegularUser
    whatherface:
        group: RegularUser
    nroz:
        group: RegularUser
    iamsam:
        group: RegularUser
    prophetoftreedor:
        group: Moderator

 

@vendetta - You should edit your post to put that in a codebox.

 

Hoo boy. You need spaces in there :B
Go here, and use that one. just copy/paste it into your config file.

Also, for the Admin group, you have the permissions:

Code:

-'*'
-'epiczones.test1.build'

Why do you have both? the -'*' permission will give the -'epiczones.test1.build' permission.
Edit: unless you mean to take the -'epiczones.test1.build' permission away from the admins. In that case, give them this permission:

Code:

                    -'-epiczones.test1.build'

 

Sorry, I'm new to permissions
My config file on the server does have spaces lol :S
It's still letting Operators use any commands, even after changing the config file to the one on pastebin and restarting the server :\

 

Do the permissions work correctly apart from giving ops access to everything? If so, it's the plugin doing it, not Permissions.

 

Try taking people out of the ops.txt? I think (Though i'm not completely sure) that OPs get all commands regardless of permissions. I'll look around some more.

 

Yes, if i de-op myself or anyone else, the Permissions apply to them. If they are an OP, they can do any commands they like, as if it's bypassing the system.

Is there a way to grant people the /give command and /kick command without being an OP (through Permissions?)

 

I think it's - 'general.give' and - 'general.kick'
Though again, I can't say for certain. Try it? :B

 

If you mean with commands, there are a couple of Permissions add-on plugins that do that.

As for ops.txt, yeah, some plugins (mine included) give ops all permissions regardless of what the Pemissions config file says.

General doesn't have a kick command. There's no way to give it to a non-op unless you have a plugin that replaces the vanilla version.

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

Okay, i've tried the 'general.time' and 'general.teleport' but nothing happens if they write it,...

 

I've tried both, and neither work :\
Is there any way to configure the Permissions plugin to not all Ops to get all commands? Or this something with Minecraft in general?

 

Put the 'general.time' and the 'general.teleport' into the Config file, and have your people type /tp -name- and /time -time-

 

No to both. It's each individual plugin that chooses whether to give commands to ops. I chose to give them to ops, because if you don't trust someone they shouldn't be an op in the first place.

Can you be more specific? Do you mean nothing happens when they type /time? If that's the case and you're using General 3.x, it's a bug in General, because if they don't have permissions it will say so.

 

What do you have to typ when you want to give a group all commands, except /setspawn for example?

so like:
- '*'
- '-/setspawn'

 

Exceptions are not possible as I recall. Sorry, but you'll have to manually give the group every command except the one you don't want them to have.

 

You might want to try the General plugin.

 

That's the thread for General 2.2; General 3.x is here.

 

I'm pretty sure that's not true. I think if you add a - within the quotes, it should take that command away. (Ex. - '-plugin.command' will make it so that the user can't use /plugin command, or whatever.)

@zwarmapapa first, putting -'/setspawn' into permissions won't work. You'll need to put in the actual node. I don't know what it is, but there's always a chance it's - 'general.setspawn'.
If it is, you'll want to put - '-general.setspawn' as the node.

Oh, thank you :B

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

Okay, I'm sorry for this noob question, but I haven't found a decent answer anywhere.

Should I NOT use the ops.txt file if I am using Permissions?

Example: I have my Permissions config file all set up with a group called Moderators, do I also need to add those users to the ops.txt file? What happens if I do? Do that essentially bypass any settings within Permissions for those users?

 

It depends on the mods you're using. Some will skip permissions if there's people in the ops.txt.

 

There seems to be the same stuff posted the last 3 pages.

Node commands you get from the plugin threads and are in form of plugin.command which has been explained earlier.

To do a good permissions file you do not give people commands a low rank and remove higher up the ranks etc unless its absolutely needed.

It's better to give permissions on a lowest gets nothing system and more as you go instead of everything then removing permissions on higher ranks and then and adding again higher up.

Don't add nodes in twice its not needed with inheritance.

Always try to make your permissions file understandable and clean with nodes and ranks last thing you want if you need to do any changes is to spend ages sorting out permissions if you added a node disabled a node then re-added a node all with inheritance.

You are NOT meant to give anyone ops unless absolutely necessary.

Ops are a default server and console thing that grants whoever is a op full access to everything as the op is there only for people maintaining the actual server configuration, files etc.

They are meant to have full override access to the system and all plugins which cannot be changed that's the whole point of a op as you need the ops when something screws up and permissions or plugins are not really are meant to stop ops using commands or having access due to this.

Its better to set your permissions up properly with a admin group and give them the commands they only need to use in there day to day administering of the server rather than oping people and only op yourself when you absolutely need to.

 

Why is it better to not give a user the - '*' command and take away a few commands? it's easier than having ten lines of permissions just to not give the -'general.time' command.

 

The * will give the user everything and any future plugins command you install.

There can be some very powerful commands that can break the server change plugin configurations etc or do stuff I'm sure you wouldn't want people using as they see fit especially general players.

Also allot of plugin commands from what I found conflict with each other so you add only the node of the plugin you want to us which in turn blocks the other plugins command.

Like essentials /motd and MCDocs /motd you add only the mcdocs command in and mcdocs is the only plugins command that is active you add the * you are conflicting those commands and any future plugins you install with commands that are the same.

Its better to know in the permissions file what you are giving people than giving them everything and removing.