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
@Pythexx
Please change your message '&2DU MÅ IKKE BYGGE HER. FAT DET.' to another one,because ymls don't like this Å very much :) Check it also here: Click
Only copy and paste it into the box and it will show you the problems in this file.
@Skaales
You have to change the groups name to default.Then it will work,if they join they will added to the specified group.I think you can change this in the permissions.yml on your root.
@Encarton
the dev build for this plugin?
if so what is the link i cant find it
@frelling
to set a negative permission for essentials the node has to look like this
"-essentials.whatever: true"
this will override the .*
I keep getting this error while enabling PermissionsBukkit:
http://pastebin.com/U0p8wuWN
Heres my config file:
http://pastebin.com/rczUqrRd
Please help me, i relly like PB.
The Dev Build links are working for me.
How do i make is so when player <insert name here> joins but is not in a group, they get added to a specific group. Get what i mean?
Also, can you please make shorten version of command to add ppl to group?
/perm player setgroup <payer> <group> is too long.
something like this maybe, idk /perm group <player> <group>
Thanks
Updated for the version 1.0.0? Thank you
@frelling
thank you so much, even though I dint get half your explaination :P
@timetoslide
This is because Essentials does not define parent permissions for essentials.*, but rather performs an internal check. In your case, even though your player has essentials.item set to false, he also inherits essentials.* from the admin group. Because Essentials does not have a parent permission that defines what essentials.* means, it is added in its raw form.
When Essentials evaluates user permissions, it first breaks the permission being checked into its constituent nodes (i.e. 'essentials' and 'item') and then checks each to determine if there is a '.*' version registered with SuperPerms. Since you have essentials.* defined in the admin group, the check always passes and never gets an opportunity to check the actual value of essentials.item.
Your best solution is to either explicitly declare each Essentials permission, or create a parent permission in the root permissions.yml file that mimics what Essentials should have done in the first place. Granted, I'll give them some slack because they also have their own permissions system and this may have been the easiest approach to maintain maximum capabilities. Yet more fodder for the Essentials Love/Hate debate.
Anyone that is experiencing problems with parent permissions - defined by plugins or in the root permissions.yml file - not applying correctly, may want to read this forum post PB Parent Permissions Fix.
can someone tell me why 1337lucas can still spawn items? http://pastebin.com/wQbksfhx using CB#1566... Essentials Dev build
I'm still having troubles with the plugin. It's not giving new players a node when they join, and that's not even considering that it wont set them to the default group...
Hi, Im having issues with The permissions. All my nodes are correct and stuff, Console aggrees with me :) just when a player logs in, The server lags then there permissions dont work, The message im getting is 'Failed to run [player_join] to permissionsbukkit' or somthing. Please help, Its only been a problem since 1.0 upgrade. Im using Cb 1550 i think, its the newest build anyway. Released only >3 days ago
@dragontailxx
I use a plugin called setrankpb, and with it i can use this node to allow my moderators to rank players up, without them being able to make people higher classes.
setrankpb.rank.rank-goes-here: true
not sure what you do to rank people up, but this works or me..
I think there should be separate nodes for building and interacting (eg. using doors, buttons and such)
I have a default rank on my server, for people that aren't "white listed" (not allowed to build) but I'd like them to be able to get out of the damn spawn building without having to have someone else come and let them out.
Is it just me or is the link to the new dev build not working
Is there any way using PermissionsBukkit alone to enable a group to only be able to set a user to a certain group. For example, my server uses a default group called newbie that has the build permission set to false, for them to be capable of building, one of my moderators or admins has to put them to the builder class, can I force it so moderators can ONLY elevate them to the builder class to avoid a moderator elevating themselves to admin randomly and editing the server's more specific functions?
@Liger_XT5
Im using CB 1337 and when you say they need to be indented once more, do you mean like below?
groups: Default: permissions: essentials.afk: true essentials.back: true essentials.back.*: true essentials.help: true essentials.home: true
and so on? Or does it also need a dash (-) like the example below?
groups: Default: permissions: - essentials.afk: true - essentials.back: true - essentials.back.*: true - essentials.help: true - essentials.home: true
regards Dave
@groveham
What CB build are you using?
Also, all the permissions need to be indented once more from the permissions line. As so: Name/Group-Name: permissions: Plugin.subnode: true
The leaving error is a normal MC error, usually means the player's client crashed or a normal network issue reared it's ugly head. No fixes for either. Just log back into the server again.
I have this error in my log when ever a player leaves the server, also players cannot access commands yet admins (who are opp'ed) can. I will paste my config file below the error. I hope someone can help. I was using permissions x3 but its inactive now =/ Also im running cb 1337. I thought the problem may be because users are not automatically added to the config file when they join for the first time, is there anyway to do this?
2011-11-27 18:32:27 [INFO] Connection reset 2011-11-27 18:32:27 [SEVERE] java.net.SocketException: Socket closed 2011-11-27 18:32:27 [INFO] tomgleave lost connection: disconnect.quitting 2011-11-27 18:32:27 [SEVERE] at java.net.SocketOutputStream.socketWrite(Unknown Source) 2011-11-27 18:32:27 [SEVERE] at java.net.SocketOutputStream.write(Unknown Source) 2011-11-27 18:32:27 [SEVERE] at java.io.BufferedOutputStream.flushBuffer(Unknown Source) 2011-11-27 18:32:27 [SEVERE] at java.io.BufferedOutputStream.flush(Unknown Source) 2011-11-27 18:32:27 [SEVERE] at java.io.DataOutputStream.flush(Unknown Source) 2011-11-27 18:32:27 [SEVERE] at net.minecraft.server.NetworkWriterThread.run(SourceFile:104)
CONFIG FILE: