Permissions
Permissions
Permissions are simple and easy to configure. SuperKits currently supports any SuperPerms-based manager, but I personally recommend bPermissions.
superkits.give - Allows users to give kits to other players via a command
superkits.list - Allows users to see available kits via a command (defaults to true)
superkits.reload - Allows users to reload kits.yml
superkits.shorttimeout - Reduces all timeouts to 30% (even global-timeout kits)
superkits.notimeout - Removes timeouts for users (even global-timeout kits)
superkits.createsign - Allows users to create and break kit selection signs
superkits.books - Allows users to save and load books via command
superkits.* - Grants all of the above permissions (defaults to OP)
Permissions for individual kits are very easy to set up as well. Every kit will default to not granting permissions if no permissions are specified, so to deny players kits, simply do not grant them access to those kits.
To grant players blanket access to a kit, give them the node superkits.kit.<kitname>.
To grant players access to take a kit only from signs, give them the node superkits.sign.<kitname>.
To grant players access to take a kit only with commands, give them the node superkits.cmd.<kitname>.
To automatically apply one of these conditions to every kit for a player, replace <kitname> with an asterisk ( * ).
When calculating permissions, SuperKits will always stack, and never cancel. This means that no explicitly stated permission can be cancelled by another granted permission - the only way to deny permissions is to simply not grant them.