bPermissions command list
These are the default commands in bPermissions
• "/permissions save" Use save after changing permissions with commands, otherwise they'll be overwritten when you reload permissions
• "/permissions reload" Do this for your permission edits to take effect
• "/permissions cleanup" This cleans out all empty users groups from your files. Any user with no permissions and simply in the default group
• "/permissions backup" This backs up all of your permission files!
To do any of these commands, you need the bPermissions.admin permission node.
You can shorten the "permissions" in these commands to "p", "bp", or "perm" .
There are two stages to the command structure for changing group/user meta data/permissions in bPermissions.
Stage 1: Select which object you would like to edit.
example: /world World_Awesome
example: /group Admin - this will create a group if it does not exist, or select an existing group with that name!
example: /user HerpDerp
You can also use /w, /g, /u as a replacement for /world, /group, /user
Stage 2: Change object as you wish, using this structure:
/OBJECT ACTION VALUE
User's available actions: addgroup, rmgroup, setgroup, addperm, rmperm, meta, cmeta
Group's available actions: addgroup, rmgroup, addperm, rmperm, meta, cmeta
World's available actions: mirror (mirrorto) (mirrorfrom)
*note: Meta data's VALUE has two arguements, KEY and VALUE. See examples below.
User examples:
example: /user rmgroup Admin This removes group "Admin" from the user selected previously.
example: /user setgroup Noob This sets the user selected to group "Noob"
example: /user rmperm some.node This removes node "some.node" from selected player
example: /user meta prefix Herp This sets meta data "prefix" to "Herp" on selected player
example: /user cmeta prefix This removes the selected player's prefix
Group examples:
example: /group addgroup Member This makes the selected group inherit group "Member"
example: /group addperm a.node This adds permission node "a.node" to the selected group.
example: /group meta suffix Derp This adds suffix "Derp" to selected group.
example: /group cmeta suffix This removes the selected group's prefix
If you use an object in a command, such as /world, /user, or /group, It will give you the currently selected object,
EX:
/world, would give the output of, "Currently selected world: yourworldnamehere"
Other commands
There are are also ways of checking the prefix / suffix of a user or a group.
example: /group meta prefix displays a groups prefix
example: /user has permissions.node checks whether a user has a specified permission
example: /user list groups will list all the groups a player is in
Shorthand commands! Great for scripts!
Ever wished you could set a group globally for a player in one line? Now you can! And you don't have to worry about the order of things either ;)
To set codename_B to admin in all worlds
/exec u:codename_B a:setgroup v:admin
To add the permission "bPermissions.admin" to the admin group in world "world"
/exec g:admin a:addperm v:bPermissions.admin w:world
- u/g: selects the user/group and provides the name
- a: provides the action (addgroup/rmgroup/setgroup/addperm/rmperm/setprefix/setsuffix/setpriority)
- v: provides the value (ie. WHAT you are adding/removing/setting)
- w: provides the world (optional, leave blank to apply to all worlds)
Quick Group Setting
To set codename_B to admin in all worlds
/setgroup codename_B admin
Hi Developers. :)
It took me a little while, but I've finally got the hang of this plugin and love it. :) But there is one thing I'd like to be able to do.
I currently have 2 worlds (multiverse) mirrored, but one of these world needs extra permissions than the other. Is there a way of just selecting a user and giving him multiple world permissions? Eg. I want him to be mod of both worlds, but I don't want to have to type in each individual permission for the group mod. Nor, do I want to give him individual permissions, as it defeats the purpose of having groups.
The mirroring is working, but I've got default users having access to commands I don't want them to have. It's supposed to be a hard classic/vanilla type of world, but having warp, home and all the rest is going to take away the "hardness" part of it.
I could have sworn I saw something somewhere that allows a group to be copied to another world.. Or am I getting my mods mixed up. :p
Any thoughts?
@Badman959
Hi. I have been running this mod for a while, then decided to try essentials group.manager. It took me ohh.. around 2 hours before I dumped the group manager again. LOL
Last night, my server had an hourly restart and then the permissions just got totally wack. It is messed up... idk what to do, I NEED HELP!!!!!!
@Badman959 Some like this should work fine for you. You don't need to remove the time set permission from default unless for some odd reason essentials is giving that to everyone by default.
@pgirl
copy paste them perms then add the ones you need to the second world
I make a groups and user like it says and then the plugin changes everything. I set the meta prefixes and nothing works.
Please either someone help me convert this or I have to stay with permbukkit
@pgirl
I would just make a third group that is almost a copy of his current one + whatever you want him to have
so instead of being a "player" your friend is a "player+1"
How can I look up what group someone is in with commands and not by opening the file?
Maybe a stupid question, but when I try to make a prefix in the Permissions.yml, it just does not work. Even when I do it ingame. I think it is because of MultiVerse, but maybe I'm doing things wrong :P Here is it:
Admin: permissions: - multiverse.access.* - bukkit.* groups: - Moderator meta: - prefix: '&4Admin'
@Odypous I have same problem but I don't have multiverse
@Odypous
My prefixes work fine with multiverse.
Where are you making them? What world are the (not) working in?
I make them in my world\groups.yml and then mirror everything to world http://pastebin.com/Rj4ry0n4 will show you one of my groups who has a working prefix (must relog if changing) also try /bp save
Prefixes can be set perworld.
I'm having an issue assigning bukkit.command.tell and essentials.msg to groups.. they aren't working but others perms are?
@Odypous
Go to your configuration files and set the global setting to true. Should work fine after that :)
is there any way to set a persons group across all worlds.
i currently run 4 worlds and it's a pita to have to change them in each world.
@fugue2005
You can mirror all users, so when you change them in one world, they auto change in all others. To do this go to your bPermissions folder, then edit the file called "mirrors.yml". So let's imagine your main world, is called "world", and your 3 other worlds are called "world2", "world3" and "world4". Then all you do is add this to your "mirrors.yml"
http://pastebin.com/2aWfqhf6
This means that "world2", "world3" and "world4", take permissions and users from "world". So every time you change permissions in "world", it will automatically apply to the 3 other worlds too :)
Hi! i really need some help cause im starting to get really pissed off here. so i type in the groups and their permissions, but then when i turn the server on it erases what i wrote and replaces it with a blank one...I just spent 30 minutes setting up a config file so i REALLY NEED AN ANSWER ASAP!!!!!!
sorry. I was a little mad right then, so my problem is i edit the groups files, then i type in the server window "permissions save" without the "". Then, when i reload the server it changes back to defaults. Please help and again i am sorry for being angry before, Thanks, -93Creeper
@93Creeper
Try saving the document before you leave it :) If not try editing it in-game using the commands provided.
@Ao1993
I've had a similar problem. After a server restart any changes made that weren't done through config have been erased.
@93Creeper
bPerms keeps a cached copy of permissions in memory, so if you edit the .yml files while your server is running, when you go to close the server or type "permissions save", bPerms will save the cached version of your permissions to the .yml files, overwriting any changes you may have made to the files. Essentially, don't edit your .yml files while the server is running.