Bukkit

Permissions

Setting up a proper permission system is essential for Cannons or your world might be bombarded and destroyed. Therefore only the OP has the permission to use a cannons at default. This prevent the accidental destruction of something when you test out this plugin. To set up Cannons I recommend a permissions plugin (e.g. PermissionsEX, example permission, minimum example).
Many of these permission can be edited in the config of the cannon design or the projectile. Therefore you can use different permissions for different designs.

cannons.*

If you are alone on your server an would like to test if something works you can use 'cannons.*' to enable all permissions necessary to use cannons.
Note: Using this option will set everything to TRUE, also the cannon build limit. So if you plan to use a maximum number of cannons you have to use cannons.player.*, cannons.projectiles.* and cannons.admin.* to do the same.

cannons.player.*

All permissions for the player. Set this to true if you don't care about permission and simple want to play. This will grant the player all necessary permissions to operate a cannon.

cannons.player.command

All commands for the player to interact with the plugin require this permission.
Default: only the operator

cannons.player.help

The permission to use the help menu.
Default: only the operator

cannons.player.rename

Allows you to rename a cannon.
Default: only the operator

cannons.player.build

Building a cannon requires a permission. If you don't have the permission you can't create a cannon. You can arrange the blocks, but it will never fire.
Default: only the operator

cannons.player.dismantle

Dismantling a cannon requires a permission. If you don't have the permission you can't deconstruct a cannon. You can break the blocks, but it will explode and you never get all the money (building costs) back. Dismantling is the only way to get a dismantling refund.
Default: only the operator
Added: v2.3

cannons.player.load

This permission is required for loading a cannon. You can load either gunpowder or a projectile. Loading a projectile requries additional permissions which are given in the config of the projectile. The default is 'cannons.projectile.default'.
Default: only the operator

cannons.player.fire

A cannon without firing is also very boring.
Default: only the operator

cannons.player.adjust

Aiming is important. Else you will hit anything. So you probably need this permission.
Default: only the operator

cannons.player.autoaim

You can also aim with autoaim. Here the cannon will turn in the direction you look. Default item for autoaim is the clock. Simply click the cannon with a clock.
Default: only the operator

cannons.player.tracking

Tracking give the possiblity to mark an enity an the cannon will automatically track it. Not implemented at the moment.
Default: only the operator

cannons.player.observer

Allows a player to add himself as observer to a cannon. He will see the impact marker of the cannon.
Default: only the operator

cannons.player.info

Allows a player to retrieve the name and design and additional information of a cannon by clicking on it.
Default: only the operator
Added: v2.2.7

cannons.player.redstone

Placing a redstone torch/repeater/wire next to a cannon allows you to fire a cannon with a button. A cannon fired with redstone has also the possibility to reload from a chest (attached to the cannon) if enabled in the config of the cannon design.
Default: only the operator

cannons.player.thermometer

Measure the temperature of the cannon barrel and see the explosion chance of the barrel.
Default: only the operator

cannons.player.ramrod

Necessary tool to clean the barrel and push the projectile.
Default: only the operator

cannons.player.autoreload

Reloading a cannon is always tiresome. If a player has this permission the cannon will automatically reload from a chest.
The player needs to be sneaking while firing the cannon. Also check if there is gunpowder and valid(!) projectiles in the chest. The cannon will always load the maximum amount of gunpowder.
Default: only the operator

cannons.player.reset

If you have a limit cannons a player can build and you don't know where your cannons are. It would be the best to delete all cannons. This permissions give you the possibility to do that. The command for this is '/cannons reset'
Default: only the operator

cannons.player.list

This is the permission for using the '/cannon list' command. Which gives you a list of all your cannons and their location.
Default: only the operator

cannons.player.target

This permission is required for the '/cannon target <mob|player|cannon>' command to change targeted entities for sentries.
Default: only the operator
Added: 2.4.3

cannons.player.whitelist

This permission is required for the '/cannon whitelist <add|remove>' command to add/remove player of a sentry whitelist.
Default: only the operator

cannons.player.claim

This permission is required for the '/cannon target <mob|player|cannon>' command to change targeted entities for sentries.
Default: only the operator
Added: 2.5.2

cannons.projectile.*

Set 'cannons.projectile.*' to activate all projectiles in 'cannons.projectile.' The default projectile node is used for all projectiles which ship with cannons. Feel free to change the permission for projectiles in the permission design file.
Note: This will not activate projectiles which are not located in 'cannons.projectile.<PROJECTILE>'.

cannons.projectile.default

The permission for all projectiles which ship with cannons. Free free to change it in the projectile design.
Default: only the operator

cannons.limit.*

This would set activate all limits, however it would be useless since limitB would overwrite everything. So please select one of the 3 possible limits and set only one.

cannons.limit.limitA

If true you can limit the amount of cannons a player can build with this permission. The amount of cannons can be set via the main config file.
Default: false

cannons.limit.limitB

Same as limitA only with a different of amounts of cannons. If both permissions are used, limit B will win.
Default: false

cannons.limit.X

To set a limit of cannons you can use also this permission. Set X to the number of cannons this player can use. The highest number of cannons is 100.
Default: false

cannons.admin.*

Use 'cannons.admin.*' to give this player all admin permissions. On default every OP on the server will have this permission.

cannons.admin.reload

If you are an admin and want to reload the cannons config without reloading the server you can use '/cannons reload'.
Default: only the operator

cannons.admin.reset

If a player spams the server with cannons use '/cannons reset NAME' to delete all his cannons'
Default: only the operator

cannons.admin.list

This permission is needed for the list command. It will show you all build cannons on the server and their location.
Default: only the operator

cannons.admin.create

Allows an admin to created a cannon just with a command for a given cannon design name.
Default: only the operator
Added: 2.3.8

cannons.admin.give

Allows an admin to give himself cannon projectiles for a given id for testing purposes.
Default: only the operator
Added: 2.4.3

cannons.admin.blockdata

Shows the blockdata of the block clicked at. Very helpful for creating new cannons.
Default: only the operator
Added: 2.5.0

cannons.admin.dismantle

The admin can dismantle all cannons, even if he is not the owner of the cannon. You can break the blocks, but it will explode and you never get all the money (building costs) back. Dismantling is the only way to get a dismantling refund.
Default: only the operator
Added: v2.3

cannons.admin.notarget

The 'notarget' flag will protect the player from being targeted by sentry cannons, similar to the creative mode. This way sentry cannons will just ignore you.
Default: only the operator
Added: v2.4.6