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!
-
View User Profile
-
Send Message
Posted Mar 27, 2013@Clinot
I discovered a bug in the plugin that's causing the tab issue. I made a comment here last night about the issue, and an updated .jar is available on my ftp site ftp.drome.us, and it should be updated here soon as well :]
-
View User Profile
-
Send Message
Posted Mar 27, 2013@Pixeldk
When giving a kit to another player the full name of the kit must be used at all times. In this case, the kit StoneDonator is actually named <yourname>:StoneDonator. You can determine this because of how it shows up in the kit list. If the kitname is preceded by a colon(:) then the kit is <yourname>:<kitname> but shortened since as the owner of the kit, you don't need to type the full name to use it on yourself.
So for your kit issue you can do 1 of 2 things :D
Let me know if this helps :]
-
View User Profile
-
Send Message
Posted Mar 27, 2013@Acedemitian
I tried to remove any possible tabs, however the plugin still refuses to load. It still gives the same error, is there anything else I can do?
-
View User Profile
-
Send Message
Posted Mar 27, 2013Thank you for the update Academician.
but now i have another problem.. sorry ;)
i can now make kits out of my inventory. and i can even give these kits to myself. the problem lies in giving this kit to my players. what i want it to do, is they are given a kit when they donate. so the server executes the command /kit StoneDonator Playername but atm, the plugin say the kit specified StoneDonator does not exist. use /lkits ect.... but if i do the command myself /kit StoneDonator . it will work. ? i tryed changing it to /kit Playername StoneDonator as you write in the commands list, /kit [username] [kitname] - Gives the requested kit to the specified player. . This do however not work. as it will say, StoneDonator is not online. so found a mistake in your commands there ;) can you help me out? think its a very small fix. and would be very happy if you fixed this. will even give you the first donation gone trough via your plugin if you get this to work within 24hours. Thank you in advance.
-
View User Profile
-
Send Message
Posted Mar 26, 2013Big apology to everyone. I've been playing with putting the code up on Git, and I added old source code from my other computer by accident, which included a bad plugin.yml which is leading to the errors everyone is receiving in the 1.5.1 version in regards to tabs in the file. I've uploaded a fix here and on my FTP site ftp.drome.us under the Release folder if anyone wants to grab it early.
-
View User Profile
-
Send Message
Posted Mar 25, 2013@Clinot
At a glance I'd say you manually edited the config file and used a tab. The YAML format doesn't allow tabs to be used at all. Check your config file and replace the tab with the appropriate amount of spaces. That should fix the issue :]
-
View User Profile
-
Send Message
Posted Mar 24, 2013When I start up my server I am getting this error: 11:53:20 AM EDT CONSOLE: [SEVERE] Could not load 'plugins\CobraKits-B8.jar' in folder 'plugins' 11:53:20 AM EDT CONSOLE: while scanning for the next token 11:53:20 AM EDT CONSOLE: '\t' that cannot start any token 11:53:20 AM EDT CONSOLE: "<reader>", line 14, column 3: 11:53:20 AM EDT CONSOLE: description: List all of the av ... 11:53:20 AM EDT CONSOLE: ^
How can i fix this?
-
View User Profile
-
Send Message
Posted Mar 20, 2013Just uploaded a beta that is compatible with the 1.5.1 Dev Build they released today, hopefully both 1.5 versions will be available soon :x
-
View User Profile
-
Send Message
Posted Mar 20, 2013@BeaztX
I just uploaded a version that's compatible with the latest 1.5 CB Development Build, hopefully it will be available later today :]
-
View User Profile
-
Send Message
Posted Mar 15, 2013Updating for 1.5 anytime soon? My KitPvP server is kinda relying on your plugin :D
-
View User Profile
-
Send Message
Posted Mar 11, 2013@MCEvolutions
Sorry for not replying to this sooner. The problem is likely that you did not change the command name in plugin.yml. The entries in there register the commands with the server, which then allow the commands to be passed to the code in the plugin when someone types it in the chat window or the console.
If you change "kit" to "claim" under the commands: heading in the plugin.yml file, it should work :D
I have no plans to add built-in aliasing, there are plenty of other plugins that do this quite well such as BetterAlias or CommandHelper.
-
View User Profile
-
Send Message
Posted Mar 3, 2013Hello,
I wanted to change the command /kit, to /claim in the source code.
When I try testing it, I type /claim <name> or /claim <name> <targetname>... Yet nothing happens and it just tells me the command usage ''/claim [kitname] [targetplayer]''
Will there be a feature in the future that allows you to specify a custom command for kits?
Thanks.
-
View User Profile
-
Send Message
Posted Mar 1, 2013@kennykyle1
Well, I could add support for kit costs, however, I am unsure if people want a basic "you need x of item y to use this kit" or if they want a specific economy plugin supported. Personally, I'd rather not bring in unneeded dependencies, and I don't run any eco plugins myself. If a basic cost system is what you had in mind, I can certainly take a look at adding it though.
-
View User Profile
-
Send Message
Posted Feb 27, 2013i want my people to buy kits! please add this feature!
-
View User Profile
-
Send Message
Posted Feb 25, 2013i wanna charge them! please add this feature !!!! This is awesome !
-
View User Profile
-
Send Message
Posted Feb 23, 2013I have submitted Beta .8 for approval by the dev.bukkit team, and updated the main plugin page. I suggest all new/old users familiarize themselves with the new features and command structure! As a note, all kits from previous CobraKits versions should be fine, I experienced no issues in upgrading my servers.
Can't wait to see all your feedback on the new update!
-
View User Profile
-
Send Message
Posted Feb 23, 2013@Clinot
After some consideration I've decided that this would be a good addition. It wasn't too tough to implement into the kit routine for v.8!
Speaking of which, I will be uploading v.8 shortly. I was considering posting it as a release, but since it has so many new features I'm going to hold off on "Release" status until maybe 1.5 to make sure we catch any issues that I didn't find in my own testing.
-
View User Profile
-
Send Message
Posted Feb 23, 2013The 1.4.6 thing was my bad, didnt see your bate download comment for 1.4.7. I was also wondering if you could make it so when you change kits it removes any potion effect. Otherwise this plugin is the perfect kit plugin.
-
View User Profile
-
Send Message
Posted Feb 19, 2013Greetings everyone,
First off sorry I have been away so long :] I am currently working on version .8 which will bring about some hefty changes for the plugin brought about by your suggestions and some bug reports I've received (mostly permissions related).
With that done I will try to answer some of these questions.
@Clinot: Please be sure you are running the v.75 1.4.6 version, the 1.4.7 version is NOT compatible and vice-versa.
@michidk: You can download a 1.4.7 compatible v.75 from ftp.drome.us, my server, until I have finished v.8.
@harlequin135: v.75 only allows you to update kits created by you, and ones currently named with the username:kitname syntax (ie harlequin135:kit1). This will be changing in v.8 with a corresponding new permission.
@IAMejegun: Looks like mismatched versions, if you are running 1.4.7 server you must use the v.75 1.4.7 from my ftp site, ftp.drome.us. 1.4.6 and 1.4.7 APIs are not compatible for what this plugin does.
I hope that catches me up :D Feel free to post or PM me if you have any further issues.
-
View User Profile
-
Send Message
Posted Feb 10, 2013This does not work with craftentity 1.4.6