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
I checked my kits.yml and everything seems to look fine. I get other similar error messages when trying to create, delete, or modify kits, or even just list them. It also gives an error when the server closes. Should I send those error messages in a ticket?
@aopell
I'll have to do some testing on my own to verify, but this actually appears to be a possible error in your kits.yml file. Did you modify it manually? Check to make sure all your kits have an Armor section. Even a kit without armor should have AIR items in each armor slot. I traced the error you are getting and it looks to me like a kit is missing the Armor section and is causing the NullPointerException.
Whenever I start my server in 1.6.2 I get this error message so I think the plugin needs to be updated to 1.6.2:
2013-07-11 12:05:24 [INFO] [CobraKits] Enabling CobraKits v1.0 2013-07-11 12:05:24 [INFO] [CobraKits] version 1.0 is loading... 2013-07-11 12:05:24 [SEVERE] java.lang.NullPointerException 2013-07-11 12:05:24 [SEVERE] at us.drome.CobraKits.Kit.<init>(Kit.java:41) 2013-07-11 12:05:24 [SEVERE] at us.drome.CobraKits.CobraKits.LoadKits(CobraKits.java:149) 2013-07-11 12:05:24 [SEVERE] at us.drome.CobraKits.CobraKits.onEnable(CobraKits.java:83) 2013-07-11 12:05:24 [SEVERE] at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:217) 2013-07-11 12:05:24 [SEVERE] at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:457) 2013-07-11 12:05:24 [SEVERE] at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:381) 2013-07-11 12:05:24 [SEVERE] at org.bukkit.craftbukkit.v1_6_R2.CraftServer.loadPlugin(CraftServer.java:282) 2013-07-11 12:05:24 [SEVERE] at org.bukkit.craftbukkit.v1_6_R2.CraftServer.enablePlugins(CraftServer.java:264) 2013-07-11 12:05:24 [SEVERE] at net.minecraft.server.v1_6_R2.MinecraftServer.l(MinecraftServer.java:313) 2013-07-11 12:05:24 [SEVERE] at net.minecraft.server.v1_6_R2.MinecraftServer.f(MinecraftServer.java:290) 2013-07-11 12:05:24 [SEVERE] at net.minecraft.server.v1_6_R2.MinecraftServer.a(MinecraftServer.java:250) 2013-07-11 12:05:24 [SEVERE] at net.minecraft.server.v1_6_R2.DedicatedServer.init(DedicatedServer.java:151) 2013-07-11 12:05:24 [SEVERE] at net.minecraft.server.v1_6_R2.MinecraftServer.run(MinecraftServer.java:391) 2013-07-11 12:05:24 [SEVERE] at net.minecraft.server.v1_6_R2.ThreadServerApplication.run(SourceFile:582)
@Chimchar3447
When you're making/updating the kit, add -g at the end of it.
Example
/ckit Standard -g
If you wanted to update it, do
/ukit Standard -g
To add potion effects, -p. Simple as that.
Basically what I'm asking is what does ambient do in the kits file.
@Chimchar3447
Do /rkit [owner].[kitname] -g Owner being the person who created the kit...
@Academician
hey how do you make a kit global Ive tried everything thxs :)
@bugattikid2012
Well I might know a possible answer to the question about the Ambient resetting to true. I had this with a few other plugins, all you need to do it stop your server, change it, then start it. Instead of just restarting it! Hope this helped. (It worked for me!) :)
I have a few quick questions.
One: What does ambient do in the kit file? I tried to set it to false, but It always sets it back to true. Two: Why does it not let me have an amplifier? I tried making myself have stuff like speed 2, but It doesn't let me. On top of this, why can't I have more time on my potions than a max of 8:00 minuites? I know it's possible to get stuff longer than that, and potion amplifiers higher than 2, as you can do it in vanilla Minecraft using /effect. Help? I would appreciate it asap! I NEED this to work properly!
Edit: I found out that you can't edit the file while the server is open, but I still don't know what ambient does. Help?
And also, just to point out bugs for your next release! Even though there is a cool-down enabled, people can just log off and then log back on again and get the kit, its really annoying, but keep up the good work. This is great plugin!
@Academician
Sounds good! :) But I was wondering, for some reason the cool-downs no longer work properly, I have it set in the config to 604800 seconds, which is a week. But it says "You can only use that kit every 504 minutes" Which is about 8 hours. So I have a problem. And then I tried to set the cool-down in-game and it crashes the server! Thanks Toby
Hello everyone, I plan to release a 1.01 build sometime next week that will have some typo fixes and some tweaks to how I handle potion effects. Including adding support for "infinite" effects.
Otherwise, 1.0 seems to be working fine with 1.6.1 servers, so no need to release a compatibility update at this time :D
@Academician
Thank you so much for your quick reply, and the good info. This is a great plugin and I will be using it a lot! :D
@hiimtoby
When specifying permissions for kits, you must use the full name if it is not a Global or Server kit. So, you need to specify "cobrakits.[owner].[kitname]", or rename the kit to be Global or Server using /rkit [owner].[kitname] -g (for global) or -sk (for server).
@Academician Hey! It still wont work, it says 'The specified kit does not exist' Even though I have updated to 1.0 and have removed the cobrakits.use and just kept the cobrakits.Member Yet when I do the /kit Member it says 'The specified kit does not exist' I have read through the information and commands multiple times. But I was wondering if it has to b a Global kit, so I tried that, but I don't know how to make a global kit. I have read through the info above but it makes no sense to me. Thanks again! :)
@hiimtoby
I would recommend reading through all the documentation provided above in the plugin post to familiarize yourself more with how the permissions work.
But, to answer your specific question, you need to hand out cobrakits.[kitname] to the person you want to access only [kitname], and remove .use from players you dont want to be able to use all kits. They will only be able to see/use [kitname] after that.
@Academician
I'm sorry to be a noob, but how do you make it so when someone donates, they get a specific kit, but no others. And I have the cooldown set to one week (604800 seconds) Because when I have the .use perm it just lets them use all kits! :) Thanks
@GoldenWrapper
There is currently no way to set it to this. I have been receiving several requests in this light and I will consider adding it in though :]
Can I make kits non-case sensitive?
@Kami675
Glad to hear it works with those plugins :] And thanks for pointing out that error, I've probably had that typo for a while :x