Bukkit

bPermissions Frequently Asked Questions

Q: Why can't I build?

A: bPermissions DOES NOT handle any build-related things by default. This will be related to another plugin you have installed like Essentials, AdminCmd, AntiGuest, Towny, WorldGuard, Residence, CommandBin, TrashCan, et al. In order to be able to build you will have to assign the relevant permission node for the plugin YOU chose to install without reading the documentation for. Go read the documentation for your plugins!

Q: Is there a '*' node in bPermissions?

A: There is not a '*' node in bPermissions. As the wildcard node is not supported in the Bukkit permissions API by default, we do not support it. Though, if a plugin supports it, you will be able to do "plugin.node.*"

Q: Why is there a groups.yml and a users.yml in the bPermissions root folder?

These are the default permission files that are used if a new world created. When a new world IS created, it gets it's permissions from the default files.

Q: What are the "group.groupname" nodes for?

These are used by worldguard for superperms group checking. They are also example nodes added to the generated files to show you how you can negate nodes as you move down inheritance trees.

• Note: You must still specify permissions in worldname/users.yml and worldname/groups.yml*

Q: What is a negative permission node?

A: Negative permission nodes are used to take away a permission from a group or player, instead of adding it to them.

Q: How to you make negative nodes in bPermissions?

A: To define a negative node in bPermissions, simply prefix it with "^". Example:

groups:
  default:
    permissions:
    - node.node   <- This is a positive node
    - ^node.node  <- This is a negative node
    groups: []

Q: How come I can't remove negative nodes with commands?

A: When removing a negative node, do not specify if it's negative. If a groups has "^node.node" in its permissions, you remove it by doing: "/world worldname" "/group grouname" "/group rmperm node.node" Notice how I specified the node without the negative assignment.

Q: How do you do prefixes and suffixes in bPermissions?

A: Prefixes and suffixes in bPermissions are quite easy, you specify them in the meta data section of each group. Here's an example:

groups:
  default:
    permissions: []
    groups: []
    meta:
      prefix: '[Default]'
      suffix: ImNoob
  admin:
    permissions: []
    groups: []
    meta:
      priority: '100'
      prefix: '[Admin]'
      suffix: ImLeet

In these two groups, they have different meta data specified. The prefix is for setting a string of text that would appear before someone's name, and the suffix is for setting text that would appear after, depending on your chat plugin set up. The priority is used for if someone has more than one group assigned to them, the group with the higher priority is the one who's prefixes and suffixes will be used. If no priority is specified, it is '0'.

Q: How do I make prefixes and suffixes work in the game chat?

A: You need a chat manager plugin. There are many to chose from, such as: bChatManager, mChat, Royal Chat, iChat, HeroChat

Q: Is there inheritance in bPermissions?

A: Yes! inheritance in bPermissions 2+ is extremely easy. Under the permissions for each group in your groups.yml file, there is a line with "group: []", simply put the groups in there that you want a group to inherit! Here's an example:

groups:
  groupA:
    permissions:
    - permission.a
    - permission.b
    groups: [] 
  groupB:
    permissions:
    - permission.c
    - permission.d
    groups:
    - groupA

In this example, groupB has groupA's permissions also, so they have permission.a, b, c and d.

Q: How do you make multiple worlds have the same permissions?

A: To have multiple worlds "mirror" their permissions, you do just that! You have to set up your mirrors in the mirror.yml file which is in the root of your bPermissions folder, which is easy. Here's an example:

world1: worldA
world2: worldA

In this example, world1 and world2 will get their permissions from worldA.

You can also use the users.yml and groups.yml from the root of the bPermissions folder as global files. To use commands on these files, select them with "/world *". World permissions will override the global files.

Q: Can I assign per-player permissions?

A: Yes! Assigning permissions to individual players is easy, you do it in your users.yml, here's an example:

users:
  HerpDerp:
    permissions:
    - some.node  
    groups:
    - somegroup

Q: How do promotion tracks work?

A: Easy! In the root of your bPermissions folder, there is a file named "tracks.yml". You specify ladders of ranks in this file, so when you do the command "/promote player-name track-name", they get promoted to the next rank in that track. There are different types of tracks, which are explained on the config.yml explanation page.

The permission node required for promoting someone on a track, is simply tracks.trackname, or tracks.* to use all tracks.

Q: Import from Permissions 3 or bPermissions 1.9.2?

Keeping the files where they were used by the older system, do these commands: "/permissions import yml" or "/permissions import p3" depending on your case.

Q: Can I run bPermissions with PermissionsEx?

A: No. Both plugins do the same thing and can not be run side-by-side.

Q: Can I run bPermissions with PermissionsBukkit?

A: No. Both plugins do the same thing and can not be run side-by-side.