General
General - a plugin for basic administrator commands
This project is now ABANDONED. However, if anyone wants to take it over, feel free to contact me either through PMs here or in the IRC at #bukkitdev (on irc.esper.net), and I'll hand over ownership of the project. Additionally, you can fork this project on github if you intend to take over.
Download:
General provides a small set of basic administrative commands for your server, such as /give, /weather, and /time.
I recommend using sk89q's CommandHelper in conjunction with this plugin. Starting from 3.4.5, there is a command-helper.txt file included with the download which you can copy to CommandHelper's config.txt for some handy aliases, such as /spawn and /home.
@PunJedi
It has recently been brought to my attention that Bukkit now sometimes gives that response for other plugins' commands in addition to its own. What I recommend is that you edit General's plugin.yml and remove any lines of the form "permission: general.permission.node" in the commands section. If what I heard is correct it should then give a more specific response telling you what permission you're lacking.
By the way, banning is not (yet) a General command. It will be, however.
@Celtic_Minstrel
I actually get the same thing. Can't ban anyone. Can only kick and mute.
Granted we are running on the dev bukkit. Seems as if some work, and then some dont, depending on the release.
Even get "I'm sorry Dave" from console. After seeing your response Ill check into more of bukkits issues possibly.
@steffan2011
That's impossible, since "I'm sorry Dave" is the result of using a vanilla command that you don't have permissions for, and only some of General's commands are liable to overwrite a vanilla command.
I've updated my server to 1.8 but by all general commands it say sorry dave i'm afraid i can't do that
I'm going to ask people to post further questions and such in the forum section rather than here on the front page.
@techwiz101
Hm, I see the issue. It's a case of trying to use something before it's loaded, and I'd guess in your case it's triggered by the default configuration being generated. There are two possibilities. Either it will work next time you try it, in which case the error was raised by trying to tell you that the config was successfully generated, or it won't work, in which case the error was triggered by trying to tell you something went wrong. Either way, you should be able to fix it by simply moving the default config.yml from the zip into the General folder.
@Lisured
I have no idea, but since General 4.0 won't have the choice anymore, it's not something I'll be adding in.
I think general.kit.* should work with PermissionsBukkit.
@Celtic_Minstrel
Bukkit seems to be working (i have CraftBukkit in comment in my config so i used it). Why there is no incorrect Permission handler warning?
EDIT: Have you implemented general.kit.* for PermissionsBukkit?
I get this on start up, I'm using PermissionsBukkit.
Try changing your permissions system to Bukkit.
@aysiyh
Which notifications?
@aysiyh
Try
/i sticky-piston
or/i stickypiston
i can't write /i sticky piston what am i suppos to write??
can you make the notifications go away?