Due to @TheYeti being busy in RL for now, I have created a new thread for Permissions 3.x. TheYeti is still part of the Permissions team.​

Permissions... Reborn.

This is a continuation of the work that was originally done by Nijikokun. All original credit goes to them as without their work this plugin would not have been possible. This plugin does not provide any commands or additional functionality beyond what is described in this post. That means that you need another plugin to provide colored names, chat prefixes, and op commands such as /give and /time.​

The Permissions Team​

The team consists of myself @rcjrrjcr and @TheYeti currently with contributions from @Nijikokun as well on occasion. There are also several other members of the community who frequently assist with providing code changes, bug fixes, patches, support, feedback, and beta testing. Special thanks to @flames and the Dynmap & Wormhole X-Treme teams for the hosting of Permissions on their Jenkins server.​

In-game commands. For a long time, users have been pestering, nagging, demanding and/or screaming for an way to manage Permissions via commands. Now, in 3.0, in-game commands are available to manage permissions and groups.

Promotion/demotion tracks. With a simple command, users can be promoted/demoted along a preconfigured track, allowing RP servers with ranks to promote the player along a class track and other possibilities.

Multigroup.

Weightage. Plugins are able to compare users via their weight, which is inherited from their groups. For example, SlapPlugin can check if Player A is higher-weighted than Player B when A tries to slap B (Not IRL, obviously).

Improved world mirroring. Config files are now split into a group file and a user file. Also, by editing storageconfig.yml, you can configure the mirroring of entire worlds, or just its users/groups. You also do not have to create files for worlds that mirror another world. Also, two different worlds can use different storage types, like YAML and SQL.

Global permissions. Instead of having to resort to cross-world group inheritance, now all worlds inherit groups and users from the global permissions file. Also, the inherited groups/users can be overridden via editing the specific world's file.

Upgrading from 2.x to 3.x

I have written a guide on GitHub. This demonstrates how to convert 2.x-style configs to 3.0. The YAML-to-SQL converter are still in testing, but it can be downloaded from here. It's written in Perl. @Zgred has created a web version of the script located here. @omgneeq is working on an Web UI for SQL databases (Sorry about the previous statement that he was making a converter.)​

First thing that you will need to do is download the plugin. Place it in your plugins/ folder and unzip it. This should create the folder Permissions and a Permissions.jar file in your plugins folder. Next, go into Permissions/ and create a folder named the same as your world. So if your world name from server.properties is Foo you will need to create the folder plugins/Permissions/Foo. You MUST rename it to whatever your world's name is or it will not work.

Note, if you have your server maps all saved into a single directory then the initial setup will be somewhat different. Say your maps are arranged in the main directory like so: bukkit/mapfolder/world1, bukkit/mapfolder/world2, etc. Then inside of the plugin/Permissions directory you will need to create a folder called mapfolder and inside of that put the directories containing users.yml and groups.yml in there.

Next, you will need to go in and add yourself to the users, just replace the user that is in there with your name. Make any other modifications that you need to. While making modifications make sure that you do NOT use tabs. These will break the YAML format and cause issues. Instead, each indent should be four spaces. If you want people who aren't in the Admin group to be able to reload the permissions plugin you need to give them 'permissions.reload' permissions within the config file.

Permissions gives server admins great control, mostly in-game reloading. More info about commands can be found here.

FAQ(Move your mouse to reveal the content)FAQ (open)FAQ (close)

[FAQ]

[Q] What is with the version numbers? I can't keep up, it seems like every time I look there is a new version![A] I use the GNU versioning system for my version numbers. So what this means is the version number should be read as Major.Minor.Revision. So for version 2.5.2 this would mean it is the 2nd Major version, the 5th Minor release in this version, and the 2nd revision. I tend to release bug fixes and anything that doesn't add functionality or will not break things as revisions. So generally you should be safe with just watching the major & minor numbers and only getting the revision if it fixes a bug specific to you. Technically 2.5.2 should have been released as 2.6 as it did add functionality, but this was below even a minor change so I released it as a revision.

[Q] I am getting an error that it can't pass BLOCK_PLACED or BLOCK _BREAK events to Permissions. Fix it![A] That's not a question. The reason why it can't place these is probably because the syntax of your Permissions file is all whacked out, or it is a different world and you don't have a config file for that world.

[Q] What am I suppose to name the config file?[A] You need to name it the same as your world. So if you look in server.properties at "level-name" you will see a world name there. Rename your config file to the same thing as that. Make sure you keep the .yml extension at the end.

[Q] Permissions are broken. Why can no one use commands? Why am I not an admin?[A] First off, make sure that your formatting is correct. Look at the format that the default config file uses. Yours should look like that. Do NOT use tabs. Use 4 spaces (IE. " " <-- Four of those things.). Also, whichever group you give the permission '*' to, do not have that group inherit permissions from anyone else. That is called overloading and it will break things. Also, this.

[Q] Which one am I suppose to download and unzip to install this?[A] Download the main package, not the JAR only. Unzip the ZIP file. The JAR only downloads are simply there for people who are UPGRADING and do not need the default config file.

[Q] I have done all of this and this doesn't work! I'm going back to GroupManager![A] Well, there is probably the problem. Make sure that you delete EssentialsGroupManager.jar and EssentialsGroupBridge.jar as these don't play well with Permissions and will cause headache.

[Q] When are you going to add <blah> <feature/command> into this already? You suck! Do what I want NAU PL0X![A] Feature requests should be posted on the GitHub tracker. Stupid suggestions like adding teleportation functionality and other less ludicrous stuff will be rejected.

Nijikokun - Without their original work this plugin would not be possible.​

All of the members of the community that regularly provide support in this thread for Permissions​

Rigby, Kainzo, DThielke, GoMySQL, sk89q, RightLegRed - For hanging out with me in IRC, tons of testing, and pushing me to improve on the code constantly and make changes to make this plugin constantly better and better, and in general being entertaining.​

Everyone else on here and in IRC who provides support, feedback, assistance, plugins that have continued to support and integrate this, and in general makes my life a bit easier, THANK YOU!​

rcjrrjcr:

I would like to thank Joy , jamesg and omgneeq for staying in #permissions for long periods of time to test out 3.0, and help me find many coding mistakes I made, patiently waiting for the next build while I fixed the bugs. I appreciate SvenBrnn 's and GoMySQL(Geoff Winans on this forum) 's help that allow me to design and code the SQL interface, and the HeroCraft coding team for providing support and some priceless IRC quotes (Dgco). Also, I would like to thank Lycano for helping me in many different aspects. Last but not least, I would like to thank Nijikokun and TheYeti for developing P2, which was one of my core plugins when I was still a 14-year-old server admin that didn't understand Java, and was the base for 3.0. Without these people, 3.0 would never be possible.​

If after reading through all of that you are still having issues do one of two things. If it is a provable bug, and you have things like screenshots or copies of startup, steps to reproduce, your craftbukkit build and the version this is running along with your config files then submit the bug on the issue tracker. If it is general help or support you are needing then post a reply to this thread and someone will try to help you.

@jungalist81 I think there's a plugin that lets buttons execute commands, or signs that do it, so you can have the sign/button do a single promotion command, or just add the user to the appropriate group instead of following a track.

Auto promote I am looking for a way for players to promote themselves from Guest to Builder in my server. I am using Permissions for my ranking system. It is used as a self-efficent tool to allow Guest become a member ingame. I am doing this because:1. I didn't want a whitelist. I don't want to have to check my email or forum or a site everyday where ppl are requesting to join my server. It would be too tedious and also I would probably approve 100% of requests anyway.2. I want guests to prove themselves. If players want to join, they must follow some instructions and do some reading ingame.

How will this work?
Guest touring around my server may choose to be able to become a member ingame. Members have the ability to play Minecraft while Guest can only roam around and visit. If they choose to become a member they must go through a dungeon. When they reach the exit, they are promoted. The Trigger can be anything as long as it works. It can be:
-when a player walks on a certain spot
-when a player punches a hanged sign

Is there a way to do this? Perhaps use it along with other plugins?

Click to expand...

Thanks for your continued help ACStache

I think a problem would be allowing Guest capable of promoting anyone (typing: /promote name). And i just want to let them only promote themselves and have the trigger reload the permissions afterwards.

On the github, I dont know which one is the permission node for the /promote command

@jungalist81 it's 'permissions.promote.<trackname>'
that way they can promote along only the track specified (if you have more than one).

edit: also with that triggercmd plugin, you can make it so a button/lever/pressure plate triggers the command. the user doesn't have to type anything and boom, command activated and it's whatever command you want it to be.

edit2: just realized with triggercmd you can still type the command out, found another plugin that might work for you too. Here is the set up info.

So now, if you've already set up your main world's groups & users yml files, this next part is easy.
For your globalUsers.yml, copy your main world's users.yml into it. If you don't have a users.yml set up yet, then the following will be the basic structure for a globalUsers.yml.

Now looking at my globalUsers.yml, you wonder, "why are the groups '- ?,<group>'? that seems silly."
What this does, is it negates the need to put anything (except "users:" on line one) of your worlds (any of them) users.yml. It also makes it so that when you join the server, it checks which world you're currently in.
It then gives you the groups permissions listed after the comma. In this case, no matter which world I join (dasbreen in this example), I'm given Owner permissions, while on the other hand no matter what world vader501 joins, he gets Mod permissions.
Ultimately - ?,<group> does [check world] then [give <group> permission]

Now you may ask, "Then how come the users.yml file is left nearly blank?". As stated above, in the globalUsers.yml, it checks your world, then gives you the globalGroups permissions that get inherited (that's explained below). No need for the users.yml.
You will also notice that as new users sign into the different worlds, the users.yml gets filled in a little. This is normal, but you need not worry about it. As I just set this up yesterday and my server is very low traffic, only 2 people have joined my main world, making my users.yml for 'world' look like this:

Code:

users: #this should be the only line you leave initially, the rest gets filled in automatically
dasbreen:
permissions: []
groups: []
amukon:
permissions: []
groups: []

Now comes where all the goodies come into play: globalGroups.yml and per world groups.yml
your globalGroups.yml is really the core of it, as this gives groups permissions across ALL worlds. Each individual world's groups.yml can add anywhere from zero extra permissions to as many as you want, as you will see. And they'll only affect the world that they're in, not all of them like the globalGroups.yml permissions. If you're going from a per world set up to global, copy the whole groups.yml that you want as the core for permissions across ALL worlds. You can go back and change the permissions later, but for now, start with that.

Mine has a lot of permissions from a lot of plugins already listed. I'm mainly getting the global infrastructure ready for when I start doing a bunch of worlds and actually start having people on my server. Doing it before you need it is always a good way to plan for future growth. I'll eventually go back and reduce a large number of these and make them per world depending on what I feel like having each world be.

As you can tell, it looks identical to how any world's groups.yml would be set up. It is, no syntax changes or little tricks like the globalUsers.yml for deciding which world you're in.

Now comes the nice part. In groups.yml for my main world, 'world', I have this as my groups.yml:

At this point, I have no chat plugin, so I have no need for prefix/suffix and can probably remove them. But again, going for the infrastructure, I keep it there so I know the full capabilities when the time comes. You may also be wondering, "What the hell is he inheriting with - '*,<group>' ?". That's simple. I'm inheriting the global version of the <group> into this world. That's how come the globalGroups.yml has no syntax changes. It's in each world that you call out to get those permissions. It's also where you change and add to the groups.yml if there's something you want to have be used in a specific world vs another. You can also do it so that globally everyone gets access to a plugin, but in one of the worlds you negate those permissions. Entirely up to you how you set it up.

Using the above example of dasbreen, I join 'world' and the globalUsers.yml tells the server that I'm part of the group: Owner. But in 'world' groups.yml, Owner doesn't have ANY permissions. "But he's inheriting himself?" No. He's inheriting everything the GLOBAL Owner gets, which in this case is pretty much everything.

If we take vader501 from above, he'll inherit 2 things: '*,Mod' & Trusted. "Why?" This bit I'm not 100% sure on, as it's a grey area for potential duplicate permissions (which would cancel out and not work), but as far as I can tell, everything is currently still working. I can't say for sure why, but I haven't seen anything break as of yet (set this up on Tuesday myself). It's making sure that he does indeed get the inheritance from the 'Trusted' group of the world, which pulls from the globalGroups.yml as well. Ultimately, he gets his permissions and all is well.

Now we take a look at the storageconfig.yml. A seemingly arbitrary file, but yet a very powerful one.
Mine looks like this:

The normal storageconfig.yml doesn't have the last 2 lines. Those lines help with setting up Global Permissions.
As mentioned before with per world groups.yml vs globalGroups.yml, you inherit the global version then can add more in each world. What the "world-inheritance:" does is inherits EVERYTHING from one specific world. In the case above, my 'world_nether' inherits all settings for groups and users straight from 'world'. And as with the groups, when you inherit, you get all of what it has to offer, and can then add even more to it!
I personally don't have anything extra in world_nether at the moment, so both the groups.yml and users.yml are blank. I would most likely, for the moment, be better off doing "worldcopy:" instead of "world-inheritance", but again, infrastructure for when I get around to adding more worlds. I would also take a guess that instead of groups inheriting '*,<group>' that they would inherit '<world>,<group>'.

In dasbreen's example it would (again, guessing on this bit) be inheriting 'world,Owner'
This inherits the permissions from Owner of 'world', which inherits from globalGroups.yml. Not the best solution, but it works none-the-less.
In vader501's example it would be inheriting both 'Trusted' as well as 'world,Mod'.

The information above was gathered and combined from Revenger on Page 71, as well as the Wiki page provided Here, with my own spin put on it (but mostly just reiterating what had already been said)

I hope this helps anyone who may have had questions about Global Permissions and didn't know of Revenger's post or the Wiki(which is in the OP).

tl;dr - start at the top, open the spoiler, and READ!! no shortcuts allowed here

Hello,
I need 2 files: users.yml and the group.yml. Can somebody write it down?
I have got problems with the orders ingame. I can't promote someone in a better group.
What's the ingame order to promote? group [NAME] [GROUP] is not running!
I have listened, permissions 3 don't need permissionsplus.
Is this right?
But the last problem is: i can't see the prefix ingame:
users.yml

1. Are the global user and group files working now in 3.1.6?
2. If yes, can i define basic groups in the global files and add users to these groups in the global users and then adding only some additional group permissions in a local group file? Or does i have to copy the whole global group definition in the local group file just to have some extra permissions in a single world?
3. And do i have to add the users in the local user file again when a use an updated local group but have the user allready added globaliy to this group?
4. And whats with the "default" group bug?

im trying to make 3 more ranks on my server called " architect " "carpenter " and "sculptor"
i want to make it so they can only spawn certain items.
ive been trying for several days now to figure it out but i give up.. could someone please take a look at this and tell me what need to be fixed

Hello,
I need 2 files: users.yml and the group.yml. Can somebody write it down?
I have got problems with the orders ingame. I can't promote someone in a better group.
What's the ingame order to promote? group [NAME] [GROUP] is not running!
I have listened, permissions 3 don't need permissionsplus.
Is this right?
But the last problem is: i can't see the prefix ingame:
users.yml

first off, to promote you'd need a track. You can use the add/remove commands found on this page.
secondly, you need a chat plugin to be able to see Prefixes/Suffixes/Colors.
lastly, you've given yourself - '*' permission in the user file and group of Admin, when Admin already has - '*' permission. Take the one out from your users file and that should ensure you don't have permission nodes not working for you.

im trying to make 3 more ranks on my server called " architect " "carpenter " and "sculptor"
i want to make it so they can only spawn certain items.
ive been trying for several days now to figure it out but i give up.. could someone please take a look at this and tell me what need to be fixed

that may be a question to post in the CommandBook thread. it looks like you're trying to use the item blacklist/whitelist. I'm not familiar with how that works, so you'd be better off asking there. As far as your permissions config set up, it looks fine. Is permissions not working or is what you're trying to achieve not working?

that may be a question to post in the CommandBook thread. it looks like you're trying to use the item blacklist/whitelist. I'm not familiar with how that works, so you'd be better off asking there. As far as your permissions config set up, it looks fine. Is permissions not working or is what you're trying to achieve not working?

Ok just so you all know, permissions 3.16 does not work with Bukkit build #946. The only people that are allowed to use ANY of the commands are the OP's like me. None of my moderators on the server can use commands because most of our MineCraft's auto-updated and didn't ask, so we had to go to build #946 for 1.7_01. If you want a user to use commands make them a op and restart your server, but be warned, they have access to all commands.

I don't know what the fuck you think you're doing for this plugin but the whole long ass command for promotion is absolute bullshit. I've already screwed up 8 times in a row trying to promote one person. You either need to get the new commands out now or this plugin is going to die very quickly.

I don't know what the fuck you think you're doing for this plugin but the whole long ass command for promotion is absolute bullshit. I've already screwed up 8 times in a row trying to promote one person. You either need to get the new commands out now or this plugin is going to die very quickly.

Click to expand...

PermissionsPlus or fork permissions and rewrite the command structure, I offered to do a rewrite but I received no support so I dropped it