Pages

Permissions

Permissions

KitMaster makes permissions easy to understand, and easy to define. Currently any SuperPerms based permission manager will work. I personally recommend PermissionsBukkit

kitmaster.give
Allows the player to give kits to other players via command. Defaults to OP.
kitmaster.list
Allows the player to see all kits available to them via command. Defaults to TRUE.
kitmaster.reload
Allows the player to use the /reloadkits command. Defaults to TRUE.
kitmaster.notimeout
Removes all timeouts for the player, including kits with global timeouts. Defaults to OP.
kitmaster.nocharge
Removes economic costs for the player if an economy is present. Defaults to OP.
kitmaster.createsign
Allows the player to create (and break) kit selection signs. Defaults to OP.
kitmaster.books
Allows the player to save and load books via command. Defaults to OP.
kitmaster.fireworks
Allows the player to save and load fireworks via command. Defaults to OP.
kitmaster.*
Gives the player all kitmaster permission nodes. Defaults to OP.

Permissions can also be defined for individual kits. Remember that KitMaster will always default to false when evaluating permissions, unless you have explicitly granted permissions. To deny permissions for a kit, simply do not grant them.

kitmaster.kit.<kitname>
Allows the player to take the specified kit via command OR from kit selection signs.
kitmaster.sign.<kitname>
Allows the player to take the specified kit ONLY from kit selection signs.
kitmaster.cmd.<kitname>
Allows the player to take the specified kit ONLY via command.

If you want one of these options to apply to EVERY kit, replace <kitname> with * (asterisk).

When calculating permissions for kits, KitMaster follows the always stack, never cancel rule. This means that there is no way to grant a permission that will revoke another permission. The only way to revoke permissions is to not grant them in the first place.

Comments

Posts Quoted:
Reply
Clear All Quotes