CobraKits
CobraKits
Version 1.1 Released!
CobraKits is a comprehensive kit plugin for Bukkit that allows admins and players alike to create kits in-game without editing any configuration files and is managable entirely by in-game commands. All you need to do is set the kit up in your own inventory and CobraKits will take care of the rest! CobraKits supports enchants, written books, named items, potion effects, and per-kit cooldowns. It also has SuperPerms support to control who can use and manage kits and change plugin settings.
Installation
- Drop the CobraKits.jar into your plugins folder and restart your server.
- The plugin will generate a CobraKits folder with a kits.yml, cooldowns.yml, and config.yml file.
- kits.yml can be edited, but please be careful! Any incorrect records will cause plugin errors.
Commands
- /ckits - This command will display usage information and offers configuration change options.
- /ckits help [command] - Display help information for all commands, or detail a command.
- /ckits current - Displays a list of the config options and their current values.
- /ckits cooldown - Toggles on/off the cooldown requirement for kits.
- /ckits duration [seconds] - Retrieves the current duration or sets it to the specified length, in seconds.
- /ckits silent - Toggles the silent flag to be on or off by default.
- /ckits concat - Toggles the concat flag to be on or off by default.
- /ckits startkit +/-[kitname] - Add/remove First Time Login Kits
- /ckits loginkit +/-[kitname] - Add/remove Login Kits
- /ckits respawnkit +/-[kitname] - Add/remove Respawn Kits
- /ckits updater - Toggles on/off the automatic update checker.
- /ckits update - Attempts to update CobraKits to the latest version.
- /kit [kitname] - Replaces the player's current inventory with the specified kit.
- -s or -silent - Does not show a message when the kit is applied.
- -c or -concat - Add the kit to the player's inventory instead of replacing it.
- -g or -global - If a Personal kit has the same name as a Global kit, use the Global kit.
- /kit [kitname] [username] - Gives the requested kit to the specified player.
- Compatible with the silent and concat flags. (The global flag is not needed as a full kitname must always be entered).
- Using/Giving a kit to a player will remove any potion/debuff effects the player is under.
- /lkit or /kits - Lists kits that the player has permission to use.
- /lkit # - Takes you to the specified kit list page. Works with either list command.
- Kit List Color Code Guide:
- Personal kits
- Server kits
- Global kits
- Other Player's Kits
- /ckit [kitname] - Turns the player's current inventory into a kit. Supports these flags:
- -cd/-cooldown [seconds] - Add a cooldown to this kit.
- -kc/-cost [itemID:amount] - Specify a kit cost, in itemID and amount needed.
- -p/-potions - Capture active potion effects on the player.
- -g/-global - Create a Global kit. (requires cobrakits.createall)
- -sk/-server - Create a Server kit. (requires cobrakits.*)
- /ukit [kitname] - Updates the kit specified to the player's current inventory. Flags:
- -cd/-cooldown [seconds] - Update a kit's cooldown, set to 0 to clear.
- -kc/-cost [itemID:amount] - Change kit cost, specify "clear" to reset it.
- -p/-potions - Update potion effects, if none are active this will clear it.
- /rkit [kitname] [newname] - Renames a kit to the given new name. Supports these Flags:
- -g/-global - Change kit owner to Global, ignores [newname]. (requires cobrakits.renameeall)
- -sk/-server - Change kit owner to Server, ignores [newname]. (requires cobrakits.renameall)
- To rename one of your Personal kits, you need to only specify the kit name. All other renames require owner.kitname format.
- /dkit [kitname] - Removes the specified kit from the plugin, this cannot be undone.
Permissions
All Permissions default to OP. All permissions with "all" inherit their lesser variant.
- cobrakits.* - Allows full access to all commands.
- cobrakits.[kitname] - Player can give themselves this specific kit.
- cobrakits.use - Grants the right to list and use self-made Personal kits, and Global kits.
- cobrakits.useall - Player can list and use any Personal or Global kit.
- cobrakits.give - Allows the ability to give other player's any kit.
- cobrakits.create - Grants the right to create a Personal kit.
- cobrakits.createall - Player can create Global kits directly.
- cobrakits.update - Allows the player to update their Personal kits.
- cobrakits.updateall - Grants access to update any Personal or Global kit.
- cobrakits.rename - Player can rename their own Personal kits.
- cobrakits.renameall - Grants the ability to rename any Personal or Global kit.
- cobrakits.delete - Player can delete their Personal kits.
- cobrakits.deleteall - Allows a player to delete any Personal or Global kit.
- cobrakits.cooldown.bypass - Grants the player the ability to bypass the cooldown setting.
- cobrakits.cooldown.bypass.[kitname] - Player bypasses the kit cooldown for this kit.
- cobrakits.cost.bypass - Grants the player the ability to not pay the cost.
- cobrakits.cost.bypass.[kitname] - Allows the player to not pay for this kit.
- cobrakits.sign.create - Player can create kit signs.
- cobrakits.sign.use - Allows the player to use a kit sign.
- cobrakits.sign.use.[kitname on sign] - Allows use of signs with specified kit name.
- cobrakits.login - Allows the player to receive Login kits.
- cobrakits.login.[kitname] - Player can receive specific Login kit.
- cobrakits.respawn - Allows the player to receive Respawn kits.
- cobrakits.respawn.[kitname] - Player can receive specific Respawn kit.
Kit Types
CobraKits has 3 kit types
- Server Kits - Meant to be used on signs or for any of the login/spawn kit settings.
- Cannot be used directly without cobrakits.* permission.
- Doesn't require "Server." in name when used for signs or login/spawn kit settings.
- Global Kits - Meant to be used for kits that most players can access.
- Requires cobrakits.use/useall to see and use them.
- Cannot be seen if the player only has cobrakits.[kitname] permissions.
- Does not require "Global." in name when used.
- Personal Kits - Kits owned/created by the players.
Potion Effects
- Specifying the -p/-potions flag while running the /ckit or /ukit commands will capture the active potion effects of the player to the kit.
- The potion effect duration is calculated on the back end, so they will be granted at full duration when using the kit later.
- If a custom potion effect length is over 8 minutes it will be preserved.
- Effects over 1638 seconds at time of kit creation/update will register as "infinite" to the game.
- There is no way to individually specify potion effects, the potions must be active on the player when captured.
- Custom effects can be added using the server's builtin /effect command.
- To clear potion effects, apply the kit, clear all potion effects (/effect [username] clear), and then update it and specify -p/-potion
- Potion effects are also affect by the -c/concat flag for /kit.
Kit Costs
- CobraKits supports a basic item trade system for kit costs that can be set with /ckit or /ukit.
- -kc/-cost [Material:amount] is the current syntax. Item durability is set to max, so players cannot trade in damaged items for a kit.
- A link to the list of Material names is included in the help section for /ckit and /ukit.
- To clear a kit cost, update the kit, after applying it to yourself, and specify -kc/-cost clear
Kit Cooldowns
- Each kit in CobraKits can have it's own individual cooldown duration.
- The global cooldown setting will override individual kit cooldowns.
- Cooldowns persist through server restart and login/logout.
- The current syntax is -cd/-cooldown [seconds]
- To clear a cooldown, update the kit, after applying it to yourself, and specify -cd/-cooldown 0
Spawn Kits
CobraKits can give Player's a kit upon login or respawn. Here's how!
- First Time Login Kits - applied to a player when they first join the server.
- Login Kits - applied to a player any time they rejoin the server. (requires permissions)
- Respawn Kits - applied to a player when they respawn on death. (requires permissions)
The directions are as follows:
- Make sure you have the correct permissions: OP or cobrakits.*
- Fill your inventory with the items/blocks you want to give to new players.
- Run /ckit -server [kitname]
- For First Time kits, run /ckits startkit +[kitname] Note: Specifying the full kit name is good practice, though Server/Global kits don't require it.
- For Login kits, run /ckits loginkit +[kitname]
- For Respawn kits, run /ckits respawnkit +[kitname]
Now that kit you created will be granted, silently, to players joining/respawning on the server. To disable the feature, run /ckits (startkit/loginkit/respawn) clear which will clear the list.
To remove a specific kit from the list, run /ckits (startkit/loginkit/respawn) -[kitname]
Kit Signs
Creating a kit sign is a simple process and has only a few rules that you need to follow! You will need:
- The correct permissions: OP, cobrakits.*, or cobrakits.sign.create
- Any kit where the full name fits on one sign line, or either a Server or Global kit.
- WorldGuard or similar plugin to protect the sign after creation.
The format for creating the signs is very simple and supports most of the /kit command functions. Place a sign and type the following on the corresponding lines:
- [COBRAKIT] or [KIT] - Capitalization not needed, but brackets are required.
- Leave this line blank, it will be replaced with the kit's cost, if any.
- kitname - Must be a full kit name that fits this line. Server or Global kits work best. No brackets or any other formatting.
- "c" and/or "s" - Here you can specify the optional concat or silent flags. As long as a "c" and/or "s" is on this line the plugin will find it.
After that is typed, create the sign. If you have everything correct the first line will turn Red, the kitname Blue, and the flags will be displayed in the format of c|s, where active options will be Gold, and inactive options will be strikeout. Any user with the cobrakits.sign.use permission will be able to use the kit sign, and it also works with the kit cooldown set in the config file, so you can prevent user's from getting kits too often.
Source Code
The source code is included in the .jar file, just open it up in a compatible archive application like 7-Zip! It is also now available on GitHub.
Feel free to submit any suggestions or problems to the tickets section or add a comment below!
@Academician
Ok just tested and confirmed that it works with lores and craftarrows I have yet to test it with Custom Enchantments though lets cross our fingers. But, I found a typo in your command listings. Where it says /kit [username] [kitname], It should actually be /kit [kitname] [username]
@Kami675
I wouldn't be able to confirm that, unfortunately, as I don't run any of those plugins. I do save the entire ItemStack object, however, so it is possible depending on their implementation...
@Academician
any chance this supports lores of any kind? like craftarrows/LoreCraft/Custom Enchantments etc?
I've just pushed 1.0 up to the dev.bukkit site, should be approved sometime soon :]
@hiimtoby
I'm expecting 1.0 to be ready either this week or next weekend.
@Academician
So do you know when it will be fixed? :)
@willschab
Change you Concat settings! :)
@Faeci
The behavior you are looking for should have been working in .9, but I probably goofed a permissions check. In 1.0 you will definitely be able to hand out only specific .[kitname] permission and have /kits show only those kits, as well as being able to use them.
I am also considering adding a category of kits just for sign use only, to free up Global kits to be only used for kits you want all users with .use to be able to access. I have no plans to add a "hidden" flag for kits at this time.
Hello Academician,
I was wondering if it is possible to make Kits for Donators .. I tried to add only:
- cobrakits.[kitname]
But then they can't use the /kits /lkit commands.
The only way these commands work is when I give them:
- cobrakits.use
Is there anyway I could make them:
- Donators only
- invisible in /kits for Non-Donators?
And can I hide the Starterkit from /kits ?
I hoped you could help me out.
Thanks.
@willschab
That is the default behavior and is spelled out clearly in the plugin description above. If you do not want items to be replaced, you must specify the -concat flag when using /kit.
@TomiCake
I will consider adding this, though the default would still be to clear all effects.
@xChrisss
The permissions idea is actually great, thanks for suggesting it. At this time I am not looking to hook into any other plugins for economy support. The cost system I am implementing for 1.0 will just be a simple item trade.
Removes players items when used...
Hi, pls make it configurable RemovePotionOnGet = false
Thanks TomiCake
Oh, and it should work with vault and economy plugins to make the kit, either from sign or command, can cost money.
Each sign should be able to have its own permission so that a player that doesn't have cobrakits.sign.use.<kitname> Can not use that sign to get the kit. ((Or what ever the permission would be))
I have just uploaded CobraKits Beta .9 to Bukkit and it is awaiting approval.
Please back up your kits.bin files before updating to .9 in case there is any error. I have not experienced any problems converting several test kit files, but be prepared just in case!
Here's the change log for what I'm calling the "Kits.YML Update"
Features I hope to include in 1.0:
@monster6286
Not at this time, no. I am considering adding it in the future. Possible implementation being that you would have to use the potions and then create the kit, so I could capture the potion effects to the kit objects that are saved.
I was wondering if it was possible to have a kit with potion effects. For example; Monkey gives you Speed 2, Jump Boost 5, Strength 1, and a bit of armor.
Update
I am very close to finishing up what I'm going to call Beta .9!
I have also made quite a few more changes which I think everyone will like, but I'll leave that for the release post.
Kit costs and per-kit cooldowns won't make it in this update, but they are still on the agenda to add.
@Kitten_Tails
The error indicates you're using the wrong version of the plugin. If you are running 1.5.2 you must run the 1.5.2 compatible build of CobraKits.
I keep getting internal errors when I try to make a kit.
09:15:31
CONSOLE:
exception executing command 'ckit' in plugin CobraKits v0.8
09:15:31
CONSOLE:
java.lang.NoClassDefFoundError: org/bukkit/craftbukkit/v1_5_R2/inventory/CraftItemStack
09:15:31
CONSOLE:
java.lang.ClassNotFoundException: org.bukkit.craftbukkit.v1_5_R2.inventory.CraftItemStack