PermissionsBukkit
PermissionsBukkit - the Official Default Groups Plugin
Current Version: v2.3 (beta v2.4)
Find PermissionsBukkit on the forums!
It's been a long time coming, but with the accomplishment of build 1000 Bukkit has finally accomplished a built-in Permissions system (codenamed Superperms). For more info on how they work, and how to integrate them with your plugin, see the official Permissions FAQ. Keep in mind that you should rarely, if ever, have to hook this plugin directly; instead keep things in the realm of checking player.hasPermission("yourplugin.node"). The FAQ thread has more info on how to use Superperms with things like chat prefixes/suffixes.
Features:
- Storage of users and groups in plugins/PermissionsBukkit/config.yml.
- Both users and groups can be assigned individual permissions and parent groups to inherit permissions from.
- Support for global and per-world permissions.
- Reload configuration from file without reloading the plugin.
- Ability to check if a player has a specific permission node.
- Ability to dump all permissions a player has and the plugins that set them.
- Ability to print plugin, description, and default for a given permission node.
- Ability to modify the permissions of groups and users and the groups of a user in-game.
- Built-in antibuild via the "permissions.build" node (defaults to allowing anyone to build).
Downloads:
Current Beta Version:
PermissionsBukkit v2.4 beta (details)
Current Version:
PermissionsBukkit v2.3 (jar) (details)
Previous Beta Version (for older than 1.7.6):
PermissionsBukkit v2.2 beta (details)
Other Important Information:
Commands
Configuration
FAQ
Changelog:
For changelog information, known caveats, and other release notes, see the entries on the files page.
Plugin Metrics
PermissionsBukkit gathers some information about your usage via PluginMetrics. The information is available here, and you can disable metrics on your server by changing 'opt-out' to true in plugins/PluginMetrics/config.yml. You can view your own stats with the /perm about command.
PermissionsBukkit collects this information about your specific usage:
- The number of groups, users, worlds, permissions, and permission roots (first parts) in your configuration.
- Whether you use per-user permissions, per-world permissions, group inheritance, and API features.
- Whether anti-build is enabled, assigned to the default group, and has a message.
- Whether debug mode or custom permissions (permissions.yml file) are in use.
- Whether the example user "ConspiracyWizard" is in your configuration (this is not a real person).
Additionally, some information is collected by PluginMetrics by default:
- Java version
- Operating system
- Authentication mode (online/offline)
- System architecture (32/64-bit) and core count
- Game version
- Server location
I see now that this plugin haven't been updated for a long time. Nevermind my question :)
I've migrated to PermissionEx instead and it works fine!
still no update to this plugin?
Hi Spacemaniac and the community! Thank you for your hard work!
I've been trying out this plugin on my server and it appears to work well except for some compatability with commandbook and multiverse. It could be that I'm missing something vital but I have read everything through several times and can't figure it out.
I'm trying to set users of the group 'moderator' only to be able to use /gamemode command in a specific world but it appears that the command doesn't work even if i set global (permissions.*: true) The only way to set gamemode is to be an OP. The superpermbridge doesn't appear to work either.
full code http://pastebin.com/KTHHDHSt
I have the latest craftbukkit and following plugins installed:
Thank you for your help! Best Regards Nick
What are the basic...BASIC perms? Like, to build, chat, and just very basic stuff.
Hey I have a question. Lets say I have worldedit installed on my server. Lets say it have the permissions worldedit.jump.other and worldedit.superpickaxe. Normal I would do worldedit.* and worldedit.jump.* but is it possible to do worldedit.*.*: true or maybe worldedit.*.*.*: true ?
When this plugin is enabled, kicking causes the server to reset. It isn't conflicting with any other plugins because I have tested this with no plugins except PB enabled...
Is it possible to add an ingame player variable for the setperm command? I.e: /permissions player setperm <me> example.node true So that whichever player executed the command gets example.node ? Thanks.
Hi. I am using your plugin and I've created a group for guests. They can't built, but they have creative game mode to fly. But there is one problem: they can place lava. They don't have permission to build, but still they can place lava and water. How to fix this?
@Nickfost
Hi Nick, I am still learning this stuff as well, the * goes at the end of a node to represent no restrictions, infinite, wildcard etc on that property, I assume by programming back ground. Still working syntax out myself, though think this is what your talking. The link I am providing is from essentials mod. Hope it helps, if not i tried.
https://github.com/essentials/Essentials/blob/master/Essentials/src/examples/permissionsex.yml
@sepukacheekray
Hi mate, think you need to set a flag for 'use' true
Whenever I type /permissions my text is completly different and does not work at all.
Here is a picture of what I get : http://i43.tinypic.com/10df7sz.png
and my config for permissionsbukkit : http://pastebin.ca/2101731
My plugins : BananaProtect, Borderguard, Buycraft, Essentials, Essentials Chat, HomeSpawnPlus, mcMMO, MobBounty, Multiverse-Core, Multiverse-Portals, NoCheat, PermissionsBukkit, Safe Creeper, WolfSpawn, WorldEdit, Worldguard.
Could someone take a look on this permissionsbukkit config.yml file: http://pastebin.com/XqBtf5XT
I have basicly made most things ": false", but it does not deny players permissions to do them. (atm a default player can do anything it seems)
I dont want players to be able to see /plugins, /help or do anything that the serverside plugins has to offer. I want that to be only for moderator/admin/owner. That would be the first step anyhow. I do want people to be able to set up a limited amount of limited sized protected zones. (worldguard+worldedit & combined with permisssionsbukkit can do that right?)
What am i doing wrong?
Why does the plugin-creators not provide a clean list of permissions? e.g. essentials you have to dig up the permissionwiki thing, and copy,paste, line up, and add value to about 250 lines!
There seems to be very much variation in wich values are true and false as default (and essentials dont even list wich). If all permissions was denied to the "default" then it would be alot easier to find wich nodes to provide whoandwhatnotgroup?
Thanks for any help anyone can give me!
Is there a way to define permissions based on a region? For instance give a player a node when they are in one area, but remove it in another? I've been looking everywhere for a plugin that can do this and I can't find one. (not just a "world.permission.node" thing either, like a "town.permission.node" type of thing)
When I disallow building rights it also disallows the right to use levers, buttons, pressure plates, etc.
Is there any way to disallow building rights but allow "usage" rights?
Are there any perms for the plugin, so that moderators cant make themselves admins, but can make default people members? I'm confused.
Update to 1.0.1 R1 please!
so.... im using yeti..... i may not understand this correctly... but how would i convert my old permisons to this system... im using mcmyadmin... but im confused.. i heard somewhere that we cant put a * on the end of certian nodes... im confused...someone help....
@GeneralShep
Here is my permissions file. http://pastebin.com/0HNMHcUV
How do you create a group?
The commands are a bit lengthy, instead of /permissions player setgroup Notch Moderator Why not have it /setgroup Notch Moderator
Much smaller, and less annoying to type :) But really its a great plugin.