boosCooldowns
Latest version: v3.9.8c
Ever wanted to set cooldowns to your warps? Ever wanted to put that /warp arena to 5 minutes cooldown while putting /warp market to 1 minute cooldown? Ever wanted to have commands for which users must pay? Or you don't want your users to teleport from pvp using /home? Then this plugin is for you! This plugin allows you to set warmups and cooldowns for every single command (even with parameters!) on your server! Configuration is extremely easy! Localization is even much easier!
For Economy and Permissions features, you need to have [Vault] on your server. You can download [Vault] HERE If you use Factions, you must set ""allowNoSlashCommand": true" to "false"! Or users will be able to use "f home" without "/" with no warmup or cooldown!
Features:
- NEW: XP costs! Charge players XP for using command (like /spawn for 10 XP levels.).
- Item costs! Charge players in items for using command (like /spawn for 20 stone etc.).
- Send player message, after using command.
- Per-permissions group warmups, cooldowns, prices, limits!
- Potion effects during command warmup!
- Command signs!
- Command aliases (player uses "/home" and command "/warp home" will be used instead - configurable!)!
- Per-life cooldowns/limits!
- Command to show limits!
- Permissions support!
- Per-command permissions!
- Command limiting! (can be used to block them too!)
- Command logging to console
- Block interaction when warming-up (can be turned on/off)
- Set warmups for commands you wish (even with parameters like /warp arena!).
- Set cooldowns for commands you wish (even with parameters like /warp arena!) .
- Set prices for commands you wish (even with parameters like /warp arena!) .
- Warmups can be canceled on damage, on move, on sneak, on sprint and on any combinations of it!
- Cooldowns/warmups are not case sensitive! So if user uses /warp arena and then /warp ARena, he will still have cooldown!
- Cooldowns can be cleared on server restart/reload
- Cooldowns can be saved on server restart, to ensure that kits with 24 hours Cooldown will be used only once per 24 hours and not after every restart!
- Easiest configuration EVER!
- Easiest localization EVER!
- Lightweight!
Commands:
- /booscooldowns reload
- Reloads config.yml.
- User needs to be OP when not using permissions, or have "booscooldowns.reload" if using permissions.
- /booscooldowns clearcooldowns <player>
- Clears all active cooldowns of given player.
- User needs to be OP when not using permissions, or have "booscooldowns.clearcooldowns" if using permissions.
- /booscooldowns clearuses <player>
- Clears how many given player used commands.
- User needs to be OP when not using permissions, or have "booscooldowns.clearuses" if using permissions.
- /booscooldowns clearwarmups <player>
- Clears all active warmups of given player.
- User needs to be OP when not using permissions, or have "booscooldowns.clearwarmups" if using permissions.
- /booscooldowns limits
- Players can use this to show their limits and how many times they still can use limited commands
- /booscooldowns set <category> <command> <value> [group]
- <category> can be cooldown, warmup, price, itemcost, xpcost, limit
- <command> can be * or any command starting with / (to add command with parameters, replace spaces with _ like /home_set)
- <value> can be number (for warmup, cooldown, price, xpcost, limit), ITEM,number (for itemcost)
- [group] can be any group, if not specified, will be set for default group
- Users with "booscooldowns.set" or OPs can use this command to set many things.
Video:
Please make some :(
Thanks to:
- Big thanks to "x8105 of SMPMinecraft.com" and "Switch0r" for awesome logos!
- phrsbrn for his helpfull and awsome pull requests on github.
- VariationVault for his video tutorial.
- All for their donations!
Please Donate:
If you like my work, please buy me a coffee or beer by clicking DONATE button at top or bottom of this page. Even 1$ is great help for me!
This plugin uses MCStats.org to collect anonymous data. Data are sent to mcstats.org where they are processed to create informative graphs for developer. MCStats is free, open source and anonymous. All data is public and freely available for every plugin. To disable data collection, set "opt-out:" to true in /plugins/PluginMetrics/config.yml.
really dying for an update here.. apparently my players have figured out how to completely bypass all warmups.. just by doing the command multiple times
This is a longshot but is it possible to do an expiration command?
Commands:
/d sheep:
cooldown: 30
warmup: 8
expires: 120
expire.command
/u
pls up tp 1.2.5...in the latest version 2.5 block interact during warm-up doesn't work..thanks for the attention
@Zombiemold
I just posted an issue about this! Oh, you where on the Towny chat yesterday! Thanks for your advise, i followed it and i found that the reason was booscooldowns.
I can also confirm that the cpu usage of booscooldowns is quite intense, and easily one of the more hard hitting plugins that I have loaded.
Boos, hopefully after you ace your exams :), you will have some time to work some of these issues out.
no i haven't . thanks, i will check it out!
@McFlicker
dude ever heard of pastebin.com?
Also generate a new config for your own needs.
sorry about that but yes if someone could copy and paste there config that would be awesome.
tell me you ign and i will give you items on my server
http://pastie.org/3721903 ON RB. And I´ll now test the Bug again.
@Zombiemold
I have to +1 the idea of linking cooldowns for a group of commands. So that a player may only, /home, /spawn, /tpa, /warp and /back (along with other teleporting commands) every X minutes. As it stands I can /spawn and the /home again without ever having to wait because those cooldowns are handled separately.
Hmm... I dont really understand the config, is everything in seconds? Anyway, I set it up but players can still use /warp HC as many times as they want without any cooldown!
Here is my config: http://pastebin.com/dScqWCKM
LordBoos,
After doing some more work with booscooldowns, there is no way that booscooldowns can truely be balanced, without being able to catch all strings after a boos-managed command.
MobArena accepts strings like "/ma jo arena jibberish blah crap" can you believe it?
The only way to balance things like this, is to have Booscooldowns accept that "/ma jo" has a cooldown and commands like "/ma join" "/ma joi" "/ma join vb word word word word" are all caught.
This is a huge flaw. Keep up the good work Boos, but we need you! :D
@levisn1 It was changed to only block access to containers. Have you tried it?
@LordBoos
in the 2.5 beta the "block interact didn't work"... now work? O.O i'm afraid to update.. xD
@Tunix2 You call this lag?
My plugin took 21ms out of 45000ms total. Thats 0,04% of all server time. Calling this lag? :O
Btw, I would love to make a donation to booscooldowns, I am really enjoying it. It is absolutely essential to our server.
Before I do though, I would like you to consider some serious suggestions.
1) There needs to be an option, to toggle how specfic warmups and cooldowns work. For instance, if I limit the command "/tell zombiemold" it only limits it if someone types "/tell zombiemold word1" and doesn't limit it for "/tell zombiemold word1 word2". I understand that if you were to make a change to booscooldowns to fix that, it would break child commands. My suggestion, is to allow us to designate certain commands to work that way, and others to work a different way t o preserver child commands, like you said. To preserver both ways.
Why is this important? Because there are lots of plugins out there with very specific functionality as far as commands go.
For instance: If a user types "/home home" it will warp him to his home which is called "home" if he types "/home home2" it will take him to his other home that is names home2. Now, if someone where to ype "/home home home home home home" the plugin warps him to his home, and ignores ALL the other homes in that string. Booscooldowns does not know how to handle this, and this is allowing players to BYPASS booscooldowns, especially if you have essentials.
There are ways around this with those other plugins, but I love booscooldowns, and would prefer to have booscooldowns handle most of our cooldown needs.
2) We need to be able to LINK commands together on the same cooldown. On my server, we have kits that people can buy with booscooldowns. in booscooldowns, I have the command "/kit" on a specific cooldown, but I would like to change it so that certain kits, have smaller cooldowns. For instance the starter kit would have a short cooldown, and the iron kit would have a longer one, but I would like them to be LINKED. So, if someone were to buy the iron kit, they couldn't ALSO buy the starter kit, because the kit would be on cooldown.
It's complicated to explain, but it's actually not that complicated of an idea.
I would be happy to donate generously to your cause if you were to consider these suggestions. If you would be willing to talk to me via IM or PM, I could explain a bit further. It's hard to explain it all in a comment.
Is there any way to link 2 commands to the same cooldown?
For instance, I want "/back" and "/return" to share cooldowns.
"/warp" "/tpa" "/spawn" would also be on the same cooldown. Is it possible with the current system?
@jaredlivingstone
There is no way for me to detect if it was accepted or not.