Bukkit

This plugin allows the creation of kits that are actually chests. When you use the /ckit KIT command, you are given 1 chest that contains the kit items. When placed into the world, the chest will contain all of the items that belong to that kit.

This plugin was created in response to a plugin request on the bukkit forums available at: http://forums.bukkit.org/threads/chest-kit.177383/

Features

Create custom kits to give to new players or whoever you want! Supports all sorts of fancy item properties, such as enchantments, display names, lore, etc. You can save your kits to the configuration file in-game. No need to mess with the configuration file unless you really want to.

Commands

• /ckit - Displays the proper want to use this command. See below.
• /ckit KITNAME - Gives you the kit named KITNAME
• /ckit create KITNAME - Creates a new kit named KITNAME. The items in the kit will be all of the items currently in your inventory.
• /ckit cooldown KITNAME COOLDOWN - Gives the existing kit named KITNAME a cooldown of COOLDOWN milliseconds (1000 = 1 second).
• /ckit delete KITNAME - Deletes the kit named KITNAME
• /ckit give PLAYERNAME KITNAME - Give PLAYERNAME the kit named KITNAME.
• /ckit save config - Save the currently defined kits to the configuration file.

All of the commands above can be run from the console by specifying a target player as follows:

• /ckit TARGETPLAYER (rest of command)

Examples:

• /ckit finalfred KITNAME - Gives finalfred the kit named KITNAME.
• /ckit finalfred create KITNAME - Creates a new kit named KITNAME that contains whatever finalfred's inventory contains.
• /ckit finalfred delete KITNAME - Deletes the kit named KITNAME.
• etc.

Permissions

• ckit.create - Allows you to use the /ckit create command (see above). Defaults to OP.
• ckit.cooldown - Allows you to use the /ckit cooldown command (see above). Defaults to OP.
• ckit.delete - Allows you to use the /ckit delete command (see above). Defaults to OP.
• ckit.save - Allows you to use the /ckit save command (see above). Defaults to OP.
• ckit.give - Allows you to use the /ckit give command (see above). Defaults to OP.
• ckit.get.* - Allows you to get any kit by using /ckit KITNAME. Defaults to OP.
• ckit.get.KITNAME - Allows you to use /ckit KITNAME. You will have to give your users this permission if you want them to spawn their own kits.

Configuration

• kits - A list of the names of each kit
• kitcooldown - A pseudo-mapping of kit names to their cooldowns in the format of a long integer. The kit "meow" will have its cooldown saved as "kitcooldown.meow"
• kititems - A pseudo-mapping of kit names to the items contained in a kit. The kit "meow" will have its item list as "kititems.meow". The list itself is a serialized list of org.bukkit.inventory.ItemStack.

I highly recommend not changing the configuration file. It's more trouble than it's worth unless you really know what you're doing. The in-game commands should suffice.

One feature you may like is that creating a kit, saving it, then deleting it will leave it's items definition in the configuration file. You can re-create the kit by manually adding the kit name back to the "kits" configuration item and it will retain all of the items it used to have. This may be useful if you accidentally delete a kit.

Enjoy!