-
Notifications
You must be signed in to change notification settings - Fork 18
Permissions
desht edited this page Aug 17, 2011
·
5 revisions
ChessCraft has been tested with Permissions 3.1.6 and 2.7.4. If you don't have Permissions installed, then Bukkit superperms will be used, so any superperms-supporting plugin can also be used, e.g. PermissionsBukkit, PermissionsEx...
If no external permissions plugin is used, then by default op-level players will have access to all commands, and non-op players will have access to the basic-level commands as listed below, i.e. non-ops will be able to create & play games.
The easiest way to assign permissions to players is as follows:
- Give administrators the chesscraft.admin privilege.
- Give players (who you want to allow to play games) the chesscraft.basic privilege.
If the above is not granular enough for you, you can assign permissions for individual ChessCraft commands to players. There is one node for each ChessCraft command:
Admin-level:
- chesscraft.commands.create.board
- chesscraft.commands.delete.board
- chesscraft.commands.delete.game
- chesscraft.commands.redraw
- chesscraft.commands.getcfg
- chesscraft.commands.setcfg
- chesscraft.commands.save
- chesscraft.commands.reload
Basic-level:
- chesscraft.commands.create.game
- chesscraft.commands.invite
- chesscraft.commands.join
- chesscraft.commands.move
- chesscraft.commands.offer.draw
- chesscraft.commands.offer.swap
- chesscraft.commands.resign
- chesscraft.commands.archive
- chesscraft.commands.tp
- chesscraft.commands.win