Project:Sandbox

If you want more control over your permissions, for example default values or children then you should consider adding them to your  plugin.yml  . This is completely optional, however it is advised. Below is an example permissions config that would be appended to the end of your existing  plugin.yml  :

""

Firstly, each permission your plugin uses is defined as a child node of the permissions node. Each permission can then optionally have a description, a default value, and children.

==== Defaults  ====

By default when a permission isn't defined for a player & nbsp;  hasPermission  & nbsp;will return false. Inside your plugin.yml you can change this by setting the default node to be one of four values:

*  true  - The permission will be true by default.

*  false  - The permission will by false by default.

*  op  - If the player is an op then this will be true.

*  not op  - If the player is not an op then this will be true.

==== Children  ====

Before now you will probably be used to the * permission to automatically assign all sub permissions. This has changed with the bukkit API and you can now define the child permissions. This allows for a lot more flexibility. Below is an example of how you do this:

""

Here the  doorman.*  permission has several child permissions assigned to it. The way child permissions work is when  doorman.*  is set to true, the child permissions are set to their values defined in the  plugin.yml . If however  doorman.*  was set to false then all child permissions would be inverted.