bPermissions
bPermissions
Welcome to bPermissions, a Superperms Manager for Bukkit! bPermissions focuses on being unique from the rest of the Permission managers. It's very simple to set up and use, it's lightning fast, fully featured, and has a great support team!
Some features:
- bPermissions has a gui client specifically designed to make running a server so easy that you'll forget that you ever used any other permissions plugin. Get it here!
- bPermissions has a unique command structure, never before seen in a permission manager. It's best used for adding lots of nodes to a user or group from the console or in-game, less typing!
- bPermissions has everything you would expect from a Permissions manager. Prefix and suffix support, inheritance, per-player permissions, multiworld support, promotion/demotion tracks, and even group priorities for multi-group setups.
- Note - bPermissions only defines prefixes and suffixes. You need a chat plugin such as bChatManager for them to show up in chat.
Commands
Say you have a user called 'Bob' and you want to put him in the group 'admin' and give him the prefix 'awesome'.
- /world yourmainworld - selects the world "yourmainworld"
- /user bob - selects the user "bob"
- /user setgroup admin - set bob's group as "admin"
- /user meta prefix awesome - set bob's prefix to "awesome"
You can do the same with groups!
- /world yourmainworld - again, selects the world
- /group admin - selects the group "admin"
- /group addgroup moderator - makes the admin group inherit from the moderator group
- /group meta prefix &c[Admin] - sets the admin prefix to "&c[Admin]"
Some other commands are as follows
- /permissions (or /bperms,/bp,/p) - general commands for bPermissions are prefixed by this
- /permissions import pex - import a pex permissions.yml in the pex folder
- /permissions reload - reloads your bPermissions files
- /permissions save - if auto-save is false, this saves your perms
- /permissions backup - backup your permissions
- /permissions helpme - for the lazy among you, this spews out some basic permissions files into your folder.
In order to use these commands, you'll need the permissions node bPermissions.admin
For configurable /promote and /demote tracks, you'll want to use permissions tracks. To read about those, visit this page
Want more commands? We have some others over on the commands page. Check 'em out!
Editing Files
bPermissions creates per world groups.yml and users.yml files in the bPermissions folder, which allow you to configure permissions on a per world basis.
Because bPermissions was designed to be configured largely via commands, bPermissions will often overwrite changes to these files especially if you /reload or restart the server.
If you've edited the files, you MUST use /permissions reload to load the modified files into the server, otherwise the permissions changes won't apply. Because a standard /reload unloads all plugins like a server stop, we cannot tell the difference between them and this will overwrite changes to your files with whatever the server last stored.
World mirroring
Worlds are mirrored like so:
world_mirroring_to: world_mirroring_from world_nether: world world_the_end: world
This duplicates the whole config for that world. Currently there's no way to have just the users or the groups mirrored, stay tuned for an update that adds this!
bPermissions and EssentialsChat
Allow me to put this issue to bed. Essentials Chat + bPermissions works for prefix and color.
This guide is for current users of EssentialsChat and want to use bPermissions along with it.
Players have colored rank prefixes and faction chat modes are also colored. All text can be colored by the players too using color codes such as &c.
bPermissions\world\groups.yml ( code snippet )
default: default groups: ## Peasant ## default: permissions: - group.default - group.userannouncer - group.userauction groups: - userannouncer - userauction meta: priority: '100' ## Citizen ## rank1: permissions: - group.default - group.rank1 groups: - default meta: priority: '200'
It has nothing configured for prefix but the group names are important (default, rank1)
Essentials\config.yml ( Code Snippet )
change-displayname: true #add-prefix-suffix: false player-commands: - chat.color - chat.format - chat.shout - chat.question chat: radius: 0 group-formats: default: '&8&lPeasant &r&8{DISPLAYNAME}&7:&r {MESSAGE}' rank1: '&8&lCitizen &r&7{DISPLAYNAME}&7:&r {MESSAGE}' moderator: '&e&l[Mod] &r&3{DISPLAYNAME}&7:&r {MESSAGE}' admin: '&c&l[Admin] &r&e{DISPLAYNAME}&7:&r {MESSAGE}'
Please direct all other Essentials support to their official support networks.
How do I get support?
First, we highly recommend you go read the FAQ page. If the answer isn't there, there's a few options of support.
- Visit the #bananacode irc channel on irc.esper.net. Just head there, as your question, and wait for someone to help you. It might be a while before you get an answer, so be patient!
- You can file a ticket. This is recommended if you don't have the time to hang around in the IRC or you have a bug report. Be prepared to check back to the ticket though, and make sure you attach your bPermissions groups and users yml files to the ticket.
- Comment on the bPermissions main page.
Note that as there's only one (slightly inactive) maintainer at the moment, any support queries may take some time.
However you choose to get support, "pls dont use txt spk," and make sure you use actual grammar.
I'm a developer!
If you wish to hook your plugin into bPermissions, please see the Developer Page for more information! If you wish to contribute code to bPermissions, fork us on GitHub!
Jenkins
Development builds of this project can now be acquired at the provided continuous integration server. These builds have not been approved by the BukkitDev staff, and are possibly buggy. Use them at your own risk.
Hi codename_B, I am using bPermissions and Towny together. The build permission node is overriding every Towny setting I have for people not to mess with wilderness areas. It gives a "cannot build in wilderness" but still lets them. Is there anyway you can let plugins override this permission and use it as a default if no other settings are present? Is this even a smart thing to allow? I truly love your plugin and would hate to have to try bukkitPermissions to see if that works (seriously that plugin is a bitch to use).
Link to ticket for Towny as well. Hopefully you two can collaborate? http://code.google.com/a/eclipselabs.org/p/towny/issues/detail?id=303&colspec=ID%20Type%20Status%20Priority%20Label%20Milestone%20Owner%20Summary
Your admirer, 5pyPig
@Viper_Infinity
You would need to setup world mirroring for every other world.
Can someone better explain world mirroring to me? i am still a bit confused..... For example: If i wanted to Mirror "SurvivalOcean" to every other worlds how would i type that in?
@feargrump
This bug was fixed in the latest bPermissions versions (which have yet to be approved on BukkitDev) you can grab them from our jenkins.
Fixed: If you using DefaultCommands, there is a dc.do node... equiv. to bPermissions.build. I hope CommandBook will coming back. Sorry for disturbing. This post can be deleted.
My rank is stuck on Admin. I set my self as Owner but it wont change from Admin to Owner. I am set as Owner in the world.yml also. I am using mChat. Here is the permission file. http://pastebin.com/nxmuaGK4 Here is the mchat file.http://pastebin.com/xGpcGR0w
@codename_B
should i be? I'll test it and get back to you.
edit: still no luck.
To keep things simple like this plugin; in the config.yml an option. Something like:
And if it's possible, line break to add multiple text line.
@Endimmion
Sure, how would you like that to work?
Will you add in the future a feature to set a text for player that haven't the build permission?
@obscurehero
Are you using override-player: true?
any idea why if I put bpermissions.build: true in a custom node in the permissions.yml...and then pass that custom node to a player they can't build...but if I just give them the node directly they can? Is this a b1185 thing?
As far as I can remember I didnt' have this issue with b1060.
hi there will bpermissions work fine with bukkits latest ver 1185?
This is my world.yml file.
http://pastebin.com/0wmRp8cm
i will test with no other plugins
It's working perfect alone, i will leave you alone and go harass Essentials team, Thank You.
@miles7191
Other plugins may be interfering - such as essentials. Please test with NO other plugins and report back to me.
Also please pastebin your whole world.yml file for me.
Bukkit Version: 1149
bpermissions Version : 1.2.5
I am unable to allow any of my players to break, place blocks. Open Chests and Doors.
I have It setup like this.
default: Player
players:
miles7191:
- VIP
groups:
VIP:
- node.node
- ^node2.node
- bPermissions.build
None of the groups are able to build, they all have those nodes. Help?
@awolfgang
You could use world mirroring?
Also - names are case sensitive.
I tried to do an Import from group manger and it transferred to the world file but when I go into the server I have no permissions. I even put in bPermissions.build and admin. also I have alot of worlds so do I have to copy the info from one world file to all the other world files?
@codename_B
<33 Thank you :D This work with permissions like Example.* right? :P
Now if when you hear me go DOH!
@IAreKyleW00t
Try stopping the server then starting it again.
EDIT: Just tested on #1149 works absolutely fine for me.