Cook
Cook 1.4 final release. Cook currently works with all future versions!
Cook
Cook is a very simple, yet very useful plugin where you can do /cook to cook the item in hand including ores and food. This is my very first own idea, and I hope all of you like it.
Commands
The only command is basically /cook!
Permissions
The only permission node for the only command is 'cook.command'. Simple as that.
GitHub Source
https://github.com/Mohammadtr/Cook-Plugin-Source Do not redistribute please!
Video
Thank you, VariationVault! Loved the video! Please report any bug you face in the comments or in a PM. If you have any suggestions, send me a PM or comment it below, thank you :D!
Mind updating for 1.7.10? Love this plugin. I use it on my server: http://s0ncraft.enjin.com/
@CraftedNight
Sure.
Could you update this plugin? Exactly what I need.
@LordEcchi
Okay. I will try to do that.
Would it be possible to include a config file, with options that would allow you to specify how often someone is able to use /cook?
For instance, someone can only use it once every 60 seconds, if they try to use it before the cooldown is over, a configurable message will be displayed and it wont work.
@kelsk1324
I will add many other things, including this one once Cook 1.4 is out
I really like this plugin, but is it possible for /cook to work on clay?
@Arkatetk
The permissions node is now 'cook.command'
@Arkatetk
I will upload a new version trying to fix your issue. Just be patient
The new version would be 1.3
@Mohammadtr I am not sure the issue, I just gave the permission cook.cook as well and it still says no access.
I have literally tried every form of the permission node: cook cook. cook.cook cook.Cook 'Cook' 'cook.cook'
Says no access. I am using bPermissions, does it not work with that?
@Arkatetk
The permissions node was changed to 'cook.Cook'
Seem to be having a issue with the permissions. I gave my users the 'cook' permission and it doesn't work. They still have no access.
@tonidu28
I cannot do /hamburger..
@Mohammadtr
Add food ( /hamburger...)
@Thegh0st2
I'll fix that ASAP :). Most probably this weekend
@iEpix
All my plugins use that format of coding. But since this plugin is very lite, I didn't really want to do a big package name. I don't have to be common to other creators. And I really think that the permission node 'cook' can make it easier for most of the bukkit users. Anyway I'm glad to know you liked it! :)
Gives an error, says major-minor version or something... Needs an update to fix.
I'm not really sure about having 'cook' as your permission node is all. Maybe have it as cook.cook.
Also, remember to name your packages with a similar format to this: tld.domainname.plugin. Again, not just 'cook'.
I do like this plugin, however. Nice job.