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.
@Sepulzera
Oh, yeah. Each line is a command/conditional, so checking for money would be like this:
$10 /^kit stuff
That would charge 10 currency and give you a kit. It's cool, really.
I should really go modify threaded execution to run each command itself in the main thread, for consistency.
Ok got it working with this hint :D
Simply put money in the first line, the command in a following ;)
@luigi_vampa
Update: Adding sign cool-downs and stopped using multiple signs at once. (For signs that wait during execution)
I'm also adding a lot more <variables> and making <variables> not case sensitive.
Also, 1.4.0 has /cs as an alias to commandsigns, so if you want you can try that out. =)
Todo:
@zonedabone
So at least my config of it was right?
I'll look out for 1.5 then.
Keep up the good work mon ami!
@luigi_vampa
I think that PermsBukkit currently has trouble with getting the group a player is in. I'll try to get 1.5.0 out tonight, which will bring back compatibility with PermsBukkit by re-adding commandsigns.group.name support.
I'm also adding a <node> operator to allow checking of any permissions node. (Helps you keep your stuff clean, because you can check for commandbook.kit perms. Also, perms checks in commandbook still work, so you coould just skip the checks on the sign and let commandbook check.
@zonedabone
Hello, I've added a pastie of my perms file if it helps
http://pastie.org/3720507
I was in the user group when I right clicked the sign. I've created three signs to access three kits: default, user and moderator. So depending on which group they are in they should be access one of the kits and using 'commandsigns.group.*' the admin should be able to access them all. Is this right?
Thanks again, Chris.
@luigi_vampa
The group system has changed in 1.4.0. I still haven't updated the documentation, but it actually checks which group the user is in, so you'll have to put the user in the user group. In pex this can be done with /pex user <name> group add user. Also, if you put people in the default group by default, make sure that the user group either extends default or you also add the user to default, as adding a group removes the default.
I think that in 1.5.0 I'll add permissions checking back to this for compatibility.
Hello Zone, love the update /#, /^ and $ are working perfectly for me but I've still got a few problems with it.
I've created this sign
line0 @user
line1 /kit user
line2 \You have been given the User kit.
The '/kit user' command works when typed in the chat bar but not through the sign. The user has 'commandsigns.group.user' permission set to true in permissionsBukkit and I've checked that I am assigned to the user group.
It gives me 'You are not in the rquired group to run this command'
Any ideas?
Thanks, Chris.
@Royalgamer06
Glad you like it! =D
@eatmybiglazer
There are 3 types of super commands. /^ runs as op, /* runs with commandsigns.permissions granted, and /# runs the command from console.
@Sepulzera
I'll do more testing on this and see what I can do. What economy are you using? Are you sure you have Vault installed and that Vault supports your economy plugin?
Commands are executed even if the player cannot afford :\
So sexy! Thanks for fixing this up! Just what I was looking for!
[EDIT] Just figured out the /^[command] setup for allowing players to run commands they can't normally. Great for fast travel!
@SkytraOne
Are you sure you typed the command right?
To do that you'd want to do something like /cs line1 /simplespleef join
At least I think that's the command syntax. CommandSigns executes commands as though they're typed by the player, so anything that only occurs with a simple plugin is on that plugin's side of things. If there is an error, I can look at it and see what's wrong, or you can post a ticket to SimpleSpleef.
Error in command execution - Command was not found in executor! Contact SimpleSpleef Programmer!
This happened when I tried to link up the join command for SimpleSpleef with a sign. However, when I link up the join command for MobArena it worked fine. Is it a problem with SimpleSpleef?
@Shocking_Cactus
What about it isn't working? The latest version has a lot of fixes, so it's worth trying again.
I can't be bothered to download since the previous versions haven't been workign for me but keep going just make it a bit more practical.
I think I'll switch signs from raw files to yml, as it will make adding new things much easier. 1.5.0 here we come!
@Neegore
Is that on the latest version?
Check your shutdown logs and see if CommandSigns logs any SEVERE messages.
@zonedabone
I'm having a problem where the signs don't save after i add the command. Of course when i add them they work, but when i restart my server, its like they shut off. Help?
That ServerSigns plugin gave me some ideas. I've already added &[color] support to messages and added %<seconds> to pause execution at any time during the script,