Command Signs
Make signs run commands!
CommandSigns allows you to assign any commands to any block making it easier for your players to do their command-based business!
Required Dependency
- Vault is required for CommandSigns. You can get it here: Vault
Features
- Run commands from signs or any other block with a single click
- Signs can have any other text on them, the commands are linked to the sign behind the scenes
- Elevate user permissions to run any command you choose
- Restrict who can use the sign and when
- Activate your CommandSigns with redstone
How To Use
- Place a sign (or block) and add any writing you want
- Add lines to your clipboard with /commandsigns line<number> <\text or /command>
- Right click the block to make it a CommandSign
Basic Tutorial
Advanced Usage (using money and permissions)
Reference Guide
Auto Updating
CommandSigns automatically checks for updates in order to keep your server up to date with the latest bug fixes! You can set CommandSigns to update completely automatically in config.yml, or to manually update, type /commandsigns update.
Videos
Video by luigi_vampa
Links
View Source on GitHub Feel free to contribute!
Help/Support
If you encounter a problem and it's not something covered by the tutorials and reference guide, please submit a trouble ticket using Bukkit's ticket requester in the menu above.
If it's something simple, post a comment and CJ will get back to you.
For some reason charging for a sign does not work, I get internal error.
I'm doing /commandsigns line0 $100
@callmemitchs
There are piston events, so I'll see what I can do. =D It'd be really cool if pistons could push CommandBlocks. I want to make sure that I do it right, however. Another current problem is breaking the block a commandSign is on.
@zonedabone
Exactly my thoughts, I used to have a command pressure plate. Also command buttons are nice.
You can also use it to make 'secret' commandsigns.
One thing I just thought of that you might need to think about with that feature is, what happens when a piston pushes a commandblock? I haven't checked how Annotate deals with this scenario, but maybe check that out?
I'll make a ticket for this now.
EDIT: Derp, guess you made one already.
@callmemitchs
I've now updated the DevBukkit page to say that Vault is a required dependency. (Over to the right >>) If this isn't big enough I'll consider adding a header. I'll also try to get to more install instructions if Frozath doesn't beat me to it.
I like the idea of adding commandsigns to any surface. In reality, it's competely possible, as CommandSigns doesn't depend at all on the presence of a sign. (It really just checks to stop people from adding to other blocks) Could you please make a ticket for this so I can milestone it for 1.6.0?
EDIT: Command... Pressure Plates? YES!
@bk871
/cs is an alias for commandsigns, though it is often overwritten by the worldedit /cs command, which runs worldedit scripts. Try using /cmds update or /commandsigns update instead. If the node, you can give an alternate node. For example, you could give the node usesign.kit and have '&usesign.kit' on your commandsign, which could then give commandbook.kit during execution with /^ or /*.
@zonedabone
You're right, I was missing the Vault plugin. I couldn't seem to find an instructions page, and Vault wasn't mentioned in this tutorial video; maybe you want to mention somewhere that it's a requirement?
So now it's all working fine and I love how streamlined it is compared to how it used to be. I did have a question though. With Annotate and Commandsigns working together, you used to be able to put a command on any block, not just a sign (by annotating the command to the block and using '/commandsign enable'). Is there any way to reproduce this functionality in the new version?
An example of how this was used on my server is that I annotated an enchantment table to make a crack of thunder whenever it was right-clicked, thus letting everyone know that someone was enchanting. :)
Anyways, amazing plugin, thanks for your help.
@zonedabone
Awesome, thanks. /cs update throws a "Script does not exist: ..." I'll download it directly, but is update.js supposed to be generated by the plugin?
I thought about using &node, however that would mean giving them access to the command without using the sign - wouldn't it?
Frozath and zonedabone, thank you both very much for your help.
Will use tickets next time.
I just wanted to announce quickly that Frozath (a good friend of mine) has kindly offered to help out on CommandSigns. Thanks for the help! =D
@bk871
@Nicomang070
This is fixed in 1.5.4, which you can get with /cs update. (After the server does an update check once every 20 minutes) Alternatively, you can reload the server and it will check, then do /cs update, or just download the file directly from here:
http://dev.bukkit.org/media/files/586/43/CommandSigns.jar
For multiple groups, you'll want to use &node to check for a permission and give that permission to both groups.
For pricing, put a line in that looks like this: '$10' where 10 is the price. (Of course without the quotes.
There are 3 elevated permissions commands, none of which are for compatibility. Each works differently. For more info, visit the commands page: http://dev.bukkit.org/server-mods/command-signs/pages/commands/
Finally, I'd like to ask that people start posting tickets for issues/feature requests, so I can categorize and milestone them.
@bk871
Here's a quick fix for you if you need it now: http://dl.dropbox.com/u/18936351/CommandSigns.jar
Otherwise, it will be in the next version.
@Frozath
I was unaware that existed, thank-you!
Variables are my only issue now.
@bk871 and Nicomang070,
http://dev.bukkit.org/server-mods/command-signs/pages/ Explains the use of #.
Also, I just confirmed some of the variables are not working, but looked at the code and it's an easy fix. I'll inform him so he can get the fix in the next version.
@Nicomang070 I'll do my best to help you, considering I'm waiting for a reply myself :)
In theory, for two commands this would work:
/commandsigns line0 <command1>
/commandsigns line1 <command2>
Regarding <NAME>, I am awaiting a reply (post below yours) - I assume we've got the same problem.
To use elevated commands, use ^ (the second command you listed). I am not sure what # does, and it's another question I asked below.
Cheers
What I am trying to do, is when you right click the sign, you get a permission. I am trying to do this through the command:
/commandsigns line0 /#manuaddp <name> hatme.hat.91
I have also tried:
/commandsigns line0 /^manuaddp <name> hatme.hat.91
It doesn't work. It just says cannot find player.
I also want to add multiple commands to 1 sign. How can I do this?
@zonedabone
Hey, I just started using this plugin yesterday, and I must say the extent of what this plugin can do is awesome. Works flawlessly thus far, however I have a few questions...
1 <NAME> does not work. It does not grab the name of the player clicking the sign, it simply outputs "<NAME>" where the name of the player should be in console. Am I missing something?
2 How do you check/allow the use of one sign to multiple groups? I've tried @group1,group2 on one line as well as @group1 and @group2 on separate lines to no avail. A single group works.
3 What is the proper way to invoke a price on the use of a sign?
4 And finally, I am aware /^command is for elevated permissions but prior versions of the plugin (the inactive one) state # is what it should be. Does # still retain any special feature, and are there any other symbols that can be used to increase the possibilities of the signs?
Cheers & keep up the great work!
@callmemitchs
Check your startup logs. Are there any errors? (For example, missing plugin.yml?)
Also, what version did you download. dozens of people are successfully running 1.5.2 and 1.5.3 on servers, and I'm running 1.5.0 on 2 of my servers.
Also, be sure that you have Vault installed (http://dev.bukkit.org/server-mods/vault/) as CommandSigns requires it to run. If not, you will get a dependency error and possibly no traceback.
More sepcifically, you'll need:
Like everyone else, my 1.2.5 server not registering the plugin,
I am having the same problem as callmemitchs, hope this gets fixed soon as i NEED this plugin
@zonedabone
Thanks for getting back to me.
I did see that the config files are no longer necessary after I posted that, however I am certain that commandsigns is installed in the right place as a .jar. Typing /commandsigns gives me the generic 'unknown command' message.
Are there any known conflicts?
ok i see him use <NAME> as a var that can be used if you dont Know the name //give (or make Console do it /#i 260 1 <NAME> this outputs "03:55:06 [INFO] Number expected, string received instead."
what im aiming to do on my Test and Production Servers,
Player A B and C want to explore a Mob Grinder, we want to give Basic Tools (Wodden sword etc)
Set a sign to say "Click for Tools" (or w/e) the sign performans /give or /i for that item to that player, but we Dont want to haveto make a Huge Arse wall of signs for every player.
how would we go about this?
ok EDIT: i had /i from commandbook wrong now using <NAME> i just get No Player matched Query. still need to get this to work as listed,