CommandHelper
CommandHelper lets you and users alias commands so that you don't get carpal tunnel, and it also allows you to script your own plugins without Java knowledge.
- Let you or users bind aliases for multiple commands
- Using an easy to use language MethodScript, script your own plugins
- Completely replace whatever you are using for /homes /warps /mail etc. with CommandHelper
- Create new features, handle new problems, without having to learn Java
- Easy to use language to pick up, with great documentation
Want an easy to use in-game map editor? Try WorldEdit. Want to protect areas? Try WorldGuard.
For the latest version: This page is not updated. For the latest builds, get them from the Downloads page.
Getting Started
Installation |
---|
Bukkit is currently required.
- Download CommandHelper and put the .jar into plugins/.
- Run your server once to generate the configuration files.
- Read the wiki (see below) to find out how to use CommandHelper.
Documentation |
---|
What are the permissions? How do you make your own scripts?
All the documentation can be found at https://methodscript.com/docs
Learning More |
---|
- Project leader: LadyCailin is the current project leader
- Lead developers: LadyCailin
- Project started: In November 2010 (Bukkit was started January 2011)
The original project leader and lead developer was sk89q.
Development builds of this project can be acquired at the provided continuous integration server. These builds have not been approved by the BukkitDev staff. Use them at your own risk.
THE COMMENTS ON THIS PAGE ARE NOT REGULARLY MONITORED. For faster support, please join us on IRC or Discord.
@Daqueh
@Adri075
@Tallcraft
How to remove the "Welcome to <server name>" message: - Open up main.ms with a text editor, - remove the bind(player_join... line until there is a ")". Remove it also. - save the file and type /reloadaliases ingame (or run it from console).
@Daqueh
To add a parameter to you /staff command, put this in your CommandHelper file: /staff $param = /ch qm staff $param This adds a command that requires one parameter. To add multiple parameters, write: /staff $ = /ch qm staff $ To use it without a parameter, also add (to you choise from above) /staff = /ch qm staff
I hope I could help you :)
@Adri075
I also have many worlds and it works fine :) Try makins this: - Have you given the permissions for CommandHelper only for the main world? - Does CommandHelper shows a notice in console when running an alias? - Have you given the permissions for any other plugin only for the main world? Also I'd like to know what message appears to you when running an alias.
PS: Does it work to use the "old" (non-alias) commands? If thst fails, CommandHelper won't be able to avoid it :)
The "Welcome to <server name>" is only appearing on my admin account. So it is not really a big problem.
Hey !
I've got two problems with commandhelper:
1. Like Daqueh said, i've got "Welcome to <server name>" with my motd.
2. All my shortcuts/aliases don't work into other world than principal one (world normal created by multiverse).
Can you help me ?
Thank you, Adrien (I'm French )
Hey! I was wondering about something.
I wanted to make "/staff" a shortcut for the command "/ch qm Staff"
Like, instead of typing /ch qm staff Hello, you could type /staff hello.
Is there any way to do this?
And also, when I installed this plugin, it says "Welcome to <server name>", how do I remove that?
Thanks!
@ryguy147
Nope! I just haven't gotten around to pushing a release, there's still several bugs in the dev version, but once those are all fixed up, and I finish the feature I'm working on, I'll be doing a release.
@ryguy147
It is working very good, so there is no need for an update in my opinion.
Is this Inactive?
@wraithguard01
That's exactly what I want to do, thanks :D
@np98765
No, that's a shortcut which basically means "turn off all permission checking for this command". It's handy for commands that you would be giving to the default group anyways.
@wraithguard01
@RealityIntern
Quick question for both of you, then:
If I use *:/alias = runas(op, command), then do I have to give any sort of permission?
@UbuntuFreak
I made a post on the forum explaining why you shouldn't do that, you can read the post here. http://forum.sk89q.com/threads/fixspleef-for-defaults.1507/#post-6006
RealityIntern's solution is the correct solution, even though yours will work.
Also, discussions like these are making me reconsider having included the ch.function.use.* series of permissions, since they offer the possibility of inadvertantly introducing a massive security vulnerability into your server, due to poor configuration on your part.
Consider the following:
If you gave everyone ch.function.use.runas, so that they could use the /tutorial command, sure, they could use it now, but they could ALSO use the /ban command. Instead, you should give each command a permission, and give each user/group access to that permission.
Now give your admins the ch.alias.admin permission. (The * permission on /tutorial means everyone can use it.) Now the commands are properly segmented into the appropriate user groups, and you didn't just introduce a massive security risk to your server.
No, just label your alias properly.
Example1: groupname:/alias = runas(op, '/cmd')
Example2: permname:/alias = runas(op, '/cmd') (give group/player ch.alias.permname permission node)
If you give people any of the func.use permission nodes, make sure to add permission/group checks in your scripts where appropriate.
@np98765
Just give the commandhelper.func.use.runas permission. To run a command as an OP, use runas('op', '/command')
Quick question...
How do I give the user permission to use runas function? I see the function permission thing in the wiki, but what is the function 'name' for runas op?
Thanks!!
Thanks you guys! Very helpful!
@tkthebeat
Yeah, It's in the main.ms file. I keep forgetting to change it so that it says "Change me in main.ms" or something. I'll add it to my todo list :)
@tkthebeat
The welcome message is a message to explain how commands can be bound to events. In this case, there is a message bound to the login event. To remove it, open up main.ms with a text editor (on Ubuntu I would use gEdit) and remove the data sausing this message.
Sorry I cannot show you the code for that because I don't have de default file anymore :)
@tkthebeat
I've wondered about that, too. I poked around in the files and couldnt find a thing, either.
I'm sure someone will respond soon - There are some very helpful users on here :D
And wraith manages it well :D
Can someone please explain how I would go about getting rid of the message that is displayed when a user logs in reading "Welcome to <Server Name>. I really like the plugin because i only know basic java and this really saves me from having to code all night, but I won't be able to use it if i can't disable that feature. I not even sure why it is in this plugin.
Can someone please point me in the right direction, any help is appreciated.
Thanks Tk
@invinciblemode The plugin works with the latest versions of bukkit, yes.