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.
@draccydragon
My mob spawning command doesn't conflict with SpawnMob. Regarding "/go home", it almost certainly doesn't do the same as MyHome's command; unless you used /setspawn self, it takes you to the location of the last bed you slept in (even if the bed isn't there anymore). And I'm not trying to force you to use it; it's there mainly because I can, with no intention of it being better than any Home plugins.
As for modularity, I've already thought about this. If there's a General 5.0, it'll almost certainly be divided up into something like six modules.
I wish this was more like classic General. All these new /go commands and dodgy permissions nodes are making things terribly confusing for my players. I have aliases in place for some things, but it's not solving every issue.
Why is this so very different from Nijikokun's plugin?
Also, if I want to use the real spawnmob plugin, how do I disable your little adaptation?
I find it very frustrating when plugin developers try to restrict players to using their versions of commands. Why would I want another way to /go home when I have MyHome (for example)?
What I'd really love is a modularized General, like what Citizens and MinecartMania did. I would like bits and pieces of what your plugin does, but some things aren't so welcome...
Set spawn's reason for not working seems to be related to setting your personal bed spawn, which is slightly odd since that's not necessary to set a world's spawn.
As for teleporting, thanks for the info, Satrosity. Perhaps that'll be able to help me fix it. Perhaps.
I have the same problem as Satrosity. It's quite confusing.
Permissions don't seem to work for Teleport and Setspawn (All other nodes seem to work). (With PermissionsBukkit)
I tried
general
general.all
general.*
general.teleport.all
I finally got it to work for all cases for teleport to work by adding these lines:
general.teleport.to.player: true
general.teleport.to.world: true
general.teleport.to.spawn: true
Setspawn seems non-responsive no matter what I try. Using /setspawn does nothing at all, I've tried many nodes but nothing seems to work. It does say that setspawn is registered to General at start up.
I could really use General's set spawn. :(
Try posting an enhancement ticket about it?
Could we get commands to set/get player level and experience? :)
I am aware of at least one issue when using General 4.x with PEX (perhaps I should've mentioned it in the 4.0.1 caveats section); however, that's related to the "*" permission (people with that permission won't be able to log in), so it doesn't sound like it's the same as your issue. If you have a stack trace, please go create a ticket and let me see it. :) Give me as much of the log relating to General as you can, preferably.
I've corrected an issue with your CH script. Here's the corrected version. http://pastie.org/2637653 (You can't put player() as a default.) Thanks for using CH!
I'm not sure when 4.0 will be released, but it'll likely be fairly soon.
When release 1.8 optimized? 3.6.3 is don't work command /kit.
@draccydragon
Not sure about the /tp command, but you're right about MOTD; there's a character limit and a line-wrapping function to prefer linewraps at a space rather than in the middle of a word. I might be able to make it more robust (since as you say the font is not fixed-width), but I would also add that making ASCII borders such as you describe is probably not an optimal choice in a variable-width font.
Feel free to file a ticket for the linewrapping so that I don't forget.
@Celtic_Minstrel
As far as I can tell, it will only respond if I specify myself as the 'player' and the other player as the 'target'. I can't just /tp 'target' with mine.
Also, I don't think your MOTD behaves the way the old General's did... It seems to have a character limit per row. Minecraft doesn't use a fixed-width font so this is really impractical. I used to be able to space out my MOTD so that it had neat little ASCII borders on both sides, but that's not possible now. I also have less space to work with in general.
An example:
The ||' in that ends up on the next line for some reason. In-game, the text is quite a bit shorter than the ==== part, and yet it overflows while the === doesn't at all.
@draccydragon
That works for me, so I'm not sure why it doesn't work for you. One possibility is that there's multiple users online whose names begin with "jo"?
@Sweetbarrow
There will be an update, eventually. It'll probably be at least a week or two, though. However, if it's truly incompatible with 1185, post a ticket with the error message you get and perhaps I'll release a bugfix update earlier.
Is this plugin inactive?
Why there is no update yet?
I found this plugin incompatible with CraftBukkit #1185
I am most distraught at my inability to "/tp jo" for "/tp myname joebob"
That used to work with the previous General. A lot has changed for the better, but this is just annoying.
@IronPython
For the bukkit sad stuff, see what I said below about the Dave errors (since it's the same source), or make sure that you have the correct permission (generally general.<name of command>). Giving general.* should work. Also make sure your config.yml says that the permissions system is Bukkit. If this doesn't help, I suggest taking this to the forum section where you could post some relevant configs and let me know things like what permissions manager you're using.
For your second question, you don't need to be op to use the /op command if you've asked General to handle it; you just need the general.op permission.
so i just updated to superprm which i know you have yet to upgrade to, so im using the bridge so that it links the two, the problem is i can only do commands if im OP even tho i did tell it to be *, i can for whatever reason still change time but any other command i try it tells me bukkit is sad (so aka dont have perm to use)
I also wanted to know if i have general.op (and my perm was working) but im not OP (reason i say this is some plugins give me to many options and i like turning OP off from time to time) can i still say /op FePython or do i need to be OP as well as have the general.op to do that command? would be nice if i didnt need to be op and still have the rights to set op know what i mean lol
@PunJedi
Any line with "permission: general.something", yes (where "something" varies). So, for example, there's "permission: general.tell" in one place, and "permission: general.give" in another.
@Celtic_Minstrel
Thank you very much. Have been wrestling with different things altogether.
Since the latest dev release, we have seen 60% less Dave, and the permissions node was an issue between class groups on PEX permissions it seems. I'll post if needed for any horrors we may find :)
Thank you again.
Update - I am bit confused at which lines I would be removing as per your post.
commands: general: permission: general.admin description: Administrates the plugin. aliases: [help, motd] usage: /general reload|die|motd|help chat.tell: permission: general.tell description: Sends another player a private message. usage: /<command> <player> <message> chat.away: permission: general.away description: Sets your away message usage: /<command> [message]
Would that mean remove anything with the permission: general and so on or the specific node you mentioned?