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.
I've put a prefix into the permissions file but whenever I promote the individual in game, the prefix doesn't come up automatically. Rather, I have to set the prefix in game.
Owner1: permissions: groups: - Administrator meta: prefix: &2[ChiefOperator]
Also, is there any easier way to promote someone rather than having to do a whole series of commands?
Quick news update
College has been extremely busy over the past couple months. Hopefully once I finish in a months time I can spend more time on bPermissions. I want to get a stable release out before I go to uni.
@tom3445
Probably a bug in the beta, I'll fix it in the next beta.
Rarely when I join (using bungeecord) i get a kick saying "bPermissions not enabled" and I lose all my permissions nodes and ranks permanently when this happens, any idea why and how to fix?
@uvbeenzaned
Might be a bug with the beta, I'll have to look into it
Are you editing groups or users?
Any reason why perms won't reload after editing the file and running /perm reload? I have to stop the server and start again every time I want to make a change via the files.
@GamersUnitedMinecraft
Found on main page here: In order to use these commands, you'll need the permissions node bPermissions.admin
That allows non-OPs to use the commands for bpermissions.
Though I'm not sure why you'd want to allow anyone to randomly alter your permissions is beyond me to be honest with you. :P
@cobwebster
Are you remembering to use the /permissions save command?
If you don't use that command after you edit perms via command, they won't save properly.
I learned that the hard way multiple times. Haha!
What are the permisions?
@rymate1234
Yeah but we still have people dropping back to default after having the rank. when I set them back into the group with the global command it fixes it. not sure why it breaks in the first place.
@cobwebster
It'll add that permission to that group in all worlds, but not all groups.
For instance, if I run the following commands:
The default group will have the essentials.tpa permission in all worlds.
If I run the following commands:
The default group will have the permission essentials.world in the survival_nether world only
@rymate1234
so If i add a permission via the /world global command it adds the permission to that group on all worlds and all groups?
@cobwebster
with global files, all of the per world files still apply, but work as additions to the global files
to promote a player across all worlds with the world commands, select the global world with /world global
I'm now using global perms for both user and group, however sometimes the ranks revert back? For example If i promote a user with the world command it still promotes their rank even though were set to only use global perms?
Would deleting any perm reference on worlds do the trick because the worlds have the same ranks as the global files.
- version 2v12 beta 18
@nhoxmax3611
@kythuat
Have you tried looking in the server log to see if there's any errors / messages from bPermissions?
why I just have config,mirrors and tracks?
I put it in a folder on the server pl, when in game press / pl, it is all red, all activities of the pl suspended. in sever 1.9.2 spigot
@kythuat @rymate1234
I can confirm that the latest (as of this post) versions work just fine on 1.9.2 Spigot servers.
@kythuat:
I would suggest giving things a try next time before "please update" posts ;P
Or asking if it's working on the version your requesting. There quite a few plugins out these days that are compatible with multiple versions of servers all straight from one plugin jar. ;)
@kythuat
Not needed, the latest betas and the last stable build should work perfectly with 1.9 and 1.9.2
please update it to 1.9.2. Thank :)