The Old Permissions is Dead - Switch to PEX (How-to)

We will no longer be developing Permissions.
Please check out PEX instead.

How to convert from P3 to PEX:

When all is done, the permissions.yml should look like this:

Code:

users:
    PsychowithanRPG:
        group:
        - Admin
    seanunited97:
        group:
        - Member
groups:
    Admin:
        permissions:
        - '*'
        - modifyworld.*
        options:
            suffix: '&8[BADASS]&7'
    Member:
        permissions:
        - god.all
        - modifyworld.*
        inheritance:
        - everyone
        options:
            prefix: '&a[G]&7'
    Guest:
        permissions:
        - lwc.blockinventory
        - groupspawn.spawn
        options:
            prefix: '&f[GUEST]&7'
        default: true

I used iChat (P2 version) instead of the bundled chat-manager to get prefixes and suffixes to work how I liked.

With permission from the original author?

There is a reason Permissions was moved to inactive, the same with GroupManager.

SuperPerms are the future. Unless you've turned Permissions into a SuperPerms manager (which I highly doubt, but you never know!) then yeah...

I feel like the whole 'rennovating code and improving ERRYTHANG' bit is a load of crap...as it usually is with any fork.

At any rate, as @codename_B asked, did you get permission to fork permissions? (no pun intended)

@codename_B We plan on adding SuperPerms support before we go gold.

You would have to ask our main developer, as he has not told us yet if he has contacted the maker.
He's currently asleep and will be back tomorrow.

Does it support transient caches?

you have definitely piqued my interest! this thread is on high alert!

Yeti's been AFK for a VERY long time

iChat wont work with this unfortunately, because it looks for a specific version #. either 2 or 3

@Cosmic Break

So... modify it Nothing they can do about it except spoof the version, which I dont even know if you can do.

i wouldnt know how to do that...

We're working on updating some key plugins by ourselves while we wait for other plugin dev's to update.

I'm not a developer, but I'm playing around with some plugins to see if I can get them working with this (I won't release builds unless I have permission).

Are you serious, another one? And it doesn't even do super perms? Thanks for adding to the mess of useless plugins and you're welcome in advance for handling all the confused admins who are going to flood IRC.

Public Service Announcement:
I strongly suggest people do not use this. It's promoting deprecated methods of using permissions and will likely give you problems. I know most devs are now releasing plugins that use only super perms and this will not work with them. You will save yourself a lot of headache if you just use PermissionsEX or PermissionsBukkit

@PermissionsTeam
Host your files externally. Don't make people have to register to download this. You are also missing a change log. Review the submission guidelines.

In fact looking at the lack of source on github and your alleged "improvements" I wouldn't be surprised if you didn't just steal the code and make no improvements.

@SwarWord You need to stop making assumptions and also to learn to read.

I will add an advisement that getting permissions for commands is not yet done.
This is in Beta Stage and is here to let people know it is being heavily worked on and improved.
We respect your criticism, and will do my best to keep people informed.

Thank You

Will developers need to support this or will it be compatible with plugins using superperms? I find it unlikely that any developer will support this.

I know how I read. I also know how to determine wether what I read is genuine or not. Either way you need to review the submission guidelines, some stuff is off.

In that case it should of been posted here.

If someone could move it to the developer section that would be great, I'm going to add the changelog and and external mirror for testers.

The developer of the plugin did not give us the GitHub login info, and he hasn't uploaded the plugin Source yet. He will do that tomorrow.

From member of team. We do not legally need permission using their binaries.

We're also making a Super Perm bridge for those who want to switch back to good ol Permissions. And some developers are working on updating it for 4.0.

http://forums.bukkit.org/threads/what-license-is-the-bukkit-project-under.154/

If you don't have permission you need to add stealcode.use to your groups file.

I will let Peanut know this when he comes on tomorrow.
Thanks for the info!

(If it is necessary we will ask the original Permissions owner (V1) if it is acceptable that we are continuing his legacy)

This thread will not be moved out here (and especially not into release) without a post here by an original Dev giving permission to continue this project, and support for the Bukkit permission API. While I won't argue whether you do or do not legal permission, we reserve the right to approve or deny plugin listings on this site.

Please do not use your own API. I want a united permissions system.

http://forums.bukkit.org/threads/ma...r-dont-use-your-own-api-use-superperms.29848/