How To Set Up Bukkit Permissions

This folio is part of the official Bukkit Documentation

This page has been accepted and included in the official Bukkit Documentation. Y'all can discuss discrepancies, issues, or errors in the article on its Talk page.

Warning: Permissions.yml is NOT a replacement Permission awarding/checking system and any permissions should go on to be handled by a plugin.

Permissions.yml is the default permission definition YAML file, automatically generated on startup. Its main part is to grouping permission nodes together into i file so that it tin can be used across the organization by permissions plugins (and plugins utilising permissions alike).

1 Parent/Child Nodes
2 Creating nodes
- 2.ane Assigning '*' Nodes
- 2.ii Setting up Permissions.yml

Parent/Child Nodes

Server admins can assign nodes to be children of another node which means that any person given a node with children will inherit those kid permissions as well.

Creating nodes

Permissions.yml allows cosmos of parent nodes for already-divers plugin permission nodes so that server administrators tin can easily distribute permissions.

A way to think of permissions.yml is like creating Kits of in-game materials, but instead of in-game tools and blocks what's being bundled is multiple permissions into ane permission node which tin can then be used in any Bukkit Permission-based organisation.

Assigning '*' Nodes

CraftBukkit's default permissions arrangement does not support '*', or wildcard nodes. This is considering the system implements a feature known as parent/child Nodes where the plugin programmer is tasked to define nodes that will act as '*' nodes rather than having a arrangement with a built in "access-all" method, which is what the OP control is used for. Permissions.yml helps server administrators consolidate permission nodes for ease of distribution in other permissions systems.

Setting upwards Permissions.yml

To begin setting upwardly your YAML file yous will get-go demand to define a new parent-node. In this example we will be using 'server.basics' followed past information technology'due south description, default value, and children with their default values.

YAML Role	Clarification	Instance
Parent Node	The defined parent-node. This is the permission y'all will put into Bukkit Permission-based plugins rather than the children nodes assigned to it.	server.basics:
`clarification:`	The clarification of the parent-node, as used by the Bukkit Help System.	`description: Bones permissions for Server.`
default:	The default value for the parent-node if its value is not prepare. The four values that can be gear up are: true, fake, op, and not-op.	`default: non-op`
`children:`	The last of the values for the parent node. Marks the start of the child node definitions.	`children:`
Kid Nodes	The value prepare for each kid node volition apply whenever the parent-node is called. The ii values that tin can exist set are: true and false.	`BukkitWiki.cmd1: true`

server.basics:        description: Bones permissions for My Cool Server.        default: true        children:           BukkitWiki.cmd1: true           BukkitWiki.cmd2: true           BukkitWiki.cmd4: true           BukkitWiki.cmd5: true