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.
@zonedabone
You say that PEX doesn't really work... What permissions plugin works the best with this plugin?
Anxiously awaiting PEX support at least, because I am running Sign Utilities which is interfering with MondoChest.
I am also using PEX
@zonedabone
In the future I want to start my second server but I am using PEX and I donĀ“t want any other perms plugin. This plugin will be one of the main plugins on my server. So when can I expect full PEX support please?
@wildkid133
Are you using PEX? Currently pex permissions don't work as expected. I do plan on adding a much more robust permissions system, but it will probably take a bit...
Is their a plan to add PEX support?
I cant get permissions to freaking work! i have tried everyhting.
Are you gonna add alias? like /cs, /csigns, /csign i dont know but the command is long. Love your plugin :)
@zxcdserf
/commandsigns remove
The right click the sign.
@zxcdserf
/commandsigns remove
The right click the sign.
I watched the video, I don't believe it explained how to remove the CommandSigns on a sign so I can remove the sign.
Ok I just made some git commits. The file should be on BukkitDev as soon as the mods approve it. (Because I would definitely hide a virus on my *open source* code)
@Royalgamer06
Oh, it has a color in it... That's going to have to be another git commit. =P
I love the plugin, thanks a bunch!
@zonedabone
Hi! Can you help me? When I have installed your plugin and I writing "/plugins" your plugin isn't showed. Why? (I have tried CB 1.2.3 R0.1 and it doesn't work. I have Permissions Bukkit but i think it doeasn't work with THIS Permissions Bukkit. If that's the point can you give me good plugin? Or good bukkit ;](I have in mind a link)
@Royalgamer06
Could you please snap a quick pic of the sign you're trying to import and make a formal ticket? Thanks.
@Qentus
Currently no, though I want to add more things to that such as /^ which will op the player during the command or /$ which will run with * node in a supported perms plugin or /> which will run as console, etc.
"Uses a new permissions node so that players can use commands they wouldn't normally have access to!" - Does it work with PEX?
@Royalgamer06
What exactly doesn't work? Are you sure you're using the latest jar?
@Royalgamer06
Not only will it do it on right click, you don't even have to be the one doing the clicking! Basically, the next time someone tries to use the sign, it will import it as long as the player has commandsigns.import. (Which is given by default) Basically, you don't have to do anything except put the new jar in!
Hope that this solution satisfies everyone - I didn't want to make it just run those signs because it wouldn't be clean; importing them automatically was the best way.
Also, I think some bugs exist with /*. I'll have to look into it and possibly make multiple versions, including temp opping the player and/or giving them the * permission with compatible plugins.
Note that the above will probably involve a Vault dependency.
Also, since I read the recent bukkit news, I've started developing for spout, or at least learning, as it is apparent that bukkit won't last forever. Hopefully I'll be able to port this plugin so everyone can enjoy it when spout is ready. (In fact, I may just write it from scratch and make an importer)