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'm going to fork this and attempt to update it to CB 1.1-R3 :3
Is there a trick to using builtin bukkit commands like /help? Even if I allow the bukkit.commands.help, I still get the message "I'm sorry, but you do not have permission to perform this command. Please contact the server administrators if you believe that this is in error." Anyone know why?
Umm, nevermind. I had entered them in config.yml as bukkit.permissions.XXX instead of bukkit.commands.XXX.
:: puts on collar of shame ::
Doesn't seem to be working for me, Every command done results in the help message.
@immacrazyaussie
mcbans.ban.global:true
D: dun move to PEx :( its a simple fix, you had no space between mcbans.ban.global: and true it needs to be : true you had :true
:( Permissionsbukkit FTW
@Sabersamus
Unfortunetly i moved to PEX
@immacrazyaussie
can you upload your config.yml? i think i know whats wrong but i would like to double check before i jump to conclusions.
Can i get some help on a problem with my YML i think
here is my severe log on start up
@GeneralShep
try putting the default group at the top, it might not work, but its always worth a shot :3 it happened to me once.
@Sh0rtC1rcuit
were you messing with the plugin.yml? :3 that may screw stuff up. what exactly are you typing? ingame and console. i may be able to help :D i have been studying this plugin (probably couldn't fork it, im no dev, but i may be able to supply support where needed)
@AdamTanner
can you upload your config.yml ? i might be able to take a look at it :3
@domingo15
this does work, i personally find it the easier permissions plugin to configure,
instead of typing - <insert_permissions_node_here> its permissions.node: true
my config needs some minor tweeking, but for the most part its pretty stable. I run into a problem that is easily fixed every once in a while. Maybe a group has a permissions they should, maybe they dont have one they should? its a really simple fix and you can do it in game/ console :) i LOVE this plugin
Hello guys I have ran into a problem that I don't know what to do. Ok so whenever i edit config.yml and then save it i get
Response: 550 The system cannot find the file specified. Error: Critical file transfer error
It only happens for config.yml on permissions bukkit every other config.yml works can someone please assist me with this problem, I have searched for fixes but have had no luck finding any so any help would be greatly appreciated.
I have problem! When new player comes to play, he isnt automaticly promoted to default group. how to fix this?
I've been having a problem with this plugin. My config file keeps resetting every time I reload or restart my server. Anyone know how to fix this?
@domingo15
This one still works great on the latest CB build.
It only does not got prefix but yo ucan solve that with a plugin.
@domingo15
Skip this one. It hasn't been updated in nearly 6 months.
Check out bpermissions. It's super stable, has a lot of options, and the dev is really active in that project.
Do this still work for craftbukkit 1.1-R3?
I'm looking for another permission that will replace PEX.
This permission would be so great if its being update like bPermission or PEX.
Are anyone else's superperm nodes all jacked up? None of mine are being detected. I know that superperms only catches plugins that are looking for legacy *.* nodes; but all of my plugins couldn't have simultaneously updated to bukkitperms at once could they?