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
Can you change global groups in game?
Shouldn't this contain tracks' commands as well?
How long does it take to perform the command /p cleanup? I am waiting for quite a while now but in the console it just said [bPermissions] Cleaning up files! but my files are still the same,nothing there were no changes in size or content.
Is there a command to edit the global files ? :l
@Enockser
"The only node you'll need to control the entire plugin (other than promotion tracks) is: bPermissions.admin"
http://dev.bukkit.org/server-mods/bpermissions/ ;)
is there an in-game command to check the group that a player is at?
@etienne702
you can create a group but you just have to select a group thats not made yet like /world world /group thenewgroup, and it should create a new group inside the groups.yml
@Enockser
the way i promote players is with a track :D i have a vip, mod, and to demote them i have a dvip, dmod track you can make tracks in the tracks.yml in the bpermissions folder the command in game to promote via track is /promote (there ign) (the track you want to use) :D
@itsMEE2
Yeah i'd like to know if there is something for that
Is there a way to select all worlds instead of every world individually, like bpermissions used to have with : /bp global addgroup group name
If not ima switch over to another permissions cause im not gonna do /world worldname /user username /user addgroup group 3 times for all my worlds.
Is there a command that can check what group a user is in?
@Ghaz_ranka
Yes instead of using - use a ^
- ^essentials.spawn
would stop them using spawn
How do you remove a prefix? I know how to set one, but I didn't find how to remove one.
@isoccerplayer
@kamskywalker
@xellois
Yeah, same questions! :-)
what dose please select a loaded world mean this happens when im trying to make an adim group plz reply♣
@hotcody1000
You need to do /world insertyourworldnamehere
Before you do any of the /user or /group commands
If I want to make it so a certain player cannot teleport people, what command would I use?
Also, If I want everyone to be able to warp, what command do I use?
@andisheh
You would type it in like this
/group rmperm (Permission node that group cannot teleport. or /user rmperm (Permission node that people cannot teleport.
And if you want people to have the same permissions without retyping it all out type
/group addgroup (Groupname)
Is it possible to add, in a next update, a command like /group setgroup [GROUPNAME] to put all players from a group into another one ?
Ok im new to bPermission and also not sure if Essentials is compatible.
What im trying to do is get the correct format for the 'groups.yml', i have and 'Admin' group, a 'Member' and a 'Default' group. To start off, i thought i would make it so 'Admin's can control time, and everyone else cant.
Here is my groups.yml, it may be all wrong i dont know because i have never used bPermissions before.
default: default
groups:
admin:
permissions:
- essentials.time.set
groups:
- member
- default
default:
permissions:
- ^essentials.time.set
groups: []
member:
permissions: []
groups: []
If someone could point me in the write direction, im sure its like learning to ride a bike :)