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.
@tcarey2015
What was the specific /exec command?
How many players were online at the time?
My server lags again when using /exec, now there is no cleanup command either right? I dont know what to do !
32.42% 4,056.14% 6.08 s 2,028.07 ms 0.0 0.0k Command: exec
Just tested it, the the negation works fine on beta16, but not on beta17
Edit: Fixed on latest build, thanks
@rymate1234
Pretty sure that the issue with negated permissions started with beta18, but I will test.
Also, I tried removing vanish.*, but the negations still had no effect. I'm OP also.
@H8llfire
There was a major change to how permissions were applied to a user in beta 17 - maybe you're being affected by that. If you revert back to beta 16, does this still happen?
@rymate1234
So if I wasn't using it, did you fix the issue either way?
Also, since beta18 negated permissions became a bit annoying, regardless of use-custom-permissible setting. For instance, granting vanish.* and then negating the effects vanish.effects.explode etc. won't work anymore. It seems like the negation doesn't overrule the wildcard when the setting is for the same group.
@H8llfire
whoops, it does default to off. my mistake
@rymate1234
It says in the changelog added option to disable (defaults to on), but the use-custom-permissible is default false. So which is it?
@H8llfire
No, true should enable it
@rymate1234
does setting use-custom-permissible to true disable it? Seems a bit counter intuitive. Also I see that you fixed it, so I guess that I will just update from ci.
@H8llfire
Ah, that'll be the new custom permissible I added.
if you disable it in the config, hopefully that error should clear itself up.
Since updating to beta 18 there seems to be a pretty critical concurrency issue that happens rarely, but randomly. It doesn't look like the fault lies with bPermissions, but this never happened before the update, it happens since the update and it happened multiple times. Basically a plugin does a (sync) setOp call, which will not work and causes following stacktrace: https://pastebin.com/9inbDNqF
@agentwolf44
Do you have any details on what may have caused this issue? (errors in the console / log files)
I haven't experienced any files being wiped in testing - if I had beta 18 wouldn't have been released!
Hey, bpermissions seems to be really buggy on the latest update... it was getting reverted back to older commands (previously saved configs basically), but worst of all is that all of the groups randomly got deleted?
Its great to see an UP TO DATE permissions plugin (PermissionsBukkit is also 1.9 but they dont support chat colors, from what i've tried at least) Thanks for continuing to develop this great plugin guys.
@cobwebster
By a dev build do you mean one of the betas on bukkitdev or a build on the jenkins?
If a Jenkins build, do you know which one?
If a bukkitdev build, I'm uploading a new beta today which may fix your issues.
@rymate1234
Our creative server just stopped also, randomly like 40% of the players online lost their rank and perms.. I had to set it to global perms.
@rymate1234
No errors, using a dev build and everything works fine. Its just I get random reports that someone hasn't got perms in a group. They're in the group and the group itself has perms. I rerun the command via console and then it works. the command being user setgroup.
@cobwebster
Any errors in console when the affected player(s) join?
I have random ranks not working, they lose perms but for some reason they still are in the rank. So the prefix works but they have none of the perms :/
Is this a common issue? Were not using global files.
It gets fixed when I set their group again via console, not in game though.