SimpleCommandSigns
Are you always teleporting that player, turning off the weather, or doing some other mundane task all the time? Are your players always forgetting commands for plugins that get used all the time? Well, with SimpleCommandSigns it is no more! Just install the plugin in your plugins directory, set up the simple config file located in the folder plugins/SimpleCommandSigns and you are ready to go! To use just right click a sign!
Features
- Commandless!
- Easy to use!
- Integrates with LWC to lock those signs
- Executes as the player that hits the sign
- Configurable
- Add the player's name to the command using the %p parameter anywhere in the command. (Example "/say %p Just rang Tux2's doorbell." would output the message: "Player just rang Tux2's doorbell.")
- Permissions (Permissions 2.x, 3.x, and Bukkit SuperPerms support)
- Will not run away and join the sponge rebellion
How to Create a Sign
- On the top line put: "[SCS]" or the custom one defined in your config file
- On the other 3 lines put the command
- If the creation is successful the top line will turn green
- Right click the sign to run the command
Permissions
- scsigns.create - the ability to create a command sign
- scsigns.use - the ablilty to use a command sign
- scsigns.autolock - have LWC autolock the sign
Need more functionality? Look no further: HiddenCommandSigns, RedstoneCommandSigns
Speaking of code, is the source available? Can't seem to find any
Edit: Never mind, I found it: http://gitorious.org/simplecommandsigns
Using command signs - is it possible for players to use commands that they wouldn't ordinarily have access to via regular permissions.. because that is what i'm looking for.
@Devil_Boy
Thanks for the fast reply! I'll play a bit with the code and see if I can figure something out. Will give you a notice if I manage to produce anything useful.
Is it possible to add economy support, where you can add a line with the charge amount to use the sign? Such as [scs] /heal %p $200
@VagueFate
I just checked the CommandBlocks source. The plugin is not as efficient as it could be. It does have an interesting config.yml database file, but it loads it every time a block is left-clicked.
If anything, I might just recode it with more features and release it under another name.
@MrYellowKay
It's been approved. Go ahead and test it out. I still have a few small things I need to add to it, but the main functionality is there, especially the permissions feature.
@estyx
In SimpleCommandSigns alone, probably not. I've been trying to keep this main plugin as simple and lightweight as possible. Getting the person to execute the command on is also difficult. This does not mean that I can't try creating a simple way of having commands on a sign run as console in a separate plugin.
Summary: It probably won't happen soon, But remind me about this later and I might find time to write something up.
@VagueFate
Perhaps I should pick up that inactive project and add my HCS permissions feature?
looks good :33 is there a way to make a block do the same? :S I really need a block to do commands because the developer of the command blocks has gone inactive. for now this will do. :P I just don't like the fact of signs everywhere ><
Edit: Nvm Command blocks works, just doesn't have a lot of features.
Great plugin! Any chance to integrate this with redstone? That would be a nice addition, being able to run commands through redstone wiring.
@Devil_Boy
Wow. An awsome explanation! I hope it gets approved very soon
@MrYellowKay
HiddenCommandSigns uses a much better method that requires that you input the required permissions. This allows the plugin to temporarily give the player the permission. Using an override node would be inefficient due to permissions being handled by each individual plugin.
Once they approve the HCS plugin and you try it, it may make more sense.
@Tux2
Oh, thank you very much! I will check it out now
Oh It will be really great if you can get the [SCS] to override permissions. Since when I added the permissions for /say, some people starts using the /say command for their own purpose. But if I don't add the permissions for /say, they cant use it. If you can do some modification, I will be really thankful to you :D
Ex: add permissions node called
- scs.use.override
and this will override the permissions and let the user use whatever command written in the sign, even though the command is not added in the permissions
Thank you :D
@MrYellowKay
As Devil_Boy pointed out there is an additional plugin he is making: HiddenCommandSigns, that will extend this plugin to do those things that you want.
@enilsss
Well I know I can do that but I only want the /say command to be enabled only when they hit sign. If I add that permission, those stupid default group guys would use /say command, making other players get confused. Cant the [SCS] override the permissions?
Once it's approved, you guys can find HiddenCommandSigns here: http://dev.bukkit.org/server-mods/hiddencommandsigns/
@methaneboy
Uh... The price should be implemented on the plugin that handles the command being run. For example: http://dev.bukkit.org/server-mods/commandpoints-essentials/
Could I request a price for some commands? Tied in with essentials economy? It would be a great help to me :)
Alright, time to address the three popular requests. ;)
I've began work on an addon plugin called HiddenCommandSigns. You can keep up with the progress by sitting in the PGDev IRC (irc://irc.mibbit.com/pinoygamers) and listening to PGDev_RSSBot. It will mainly alias the real command to be executed with the text on the sign, which is a much more fool-proof method than having a database that needs to track sign locations.
@TTlabambaTT When you're setting the real command behind the sign, you can specify multiple commands to be executed sequentially.
@MicoMine @HugoNoob The commands will be hidden in a matter that allows you to put anything you want on the original commandsign, because that text is no longer the one being executed.
@therealorgrin @MrYellowKay @Spaceshipable I think I've found the most appropriate way of allowing this. It'll involve you inputting the required permission(s) though. When they hit the sign, they'll temporarily be given the perms. I should be able to maintain the same Permissions supports as SimpleCommandSigns.
is there anyway to allow the player to hit a sign an op has made despite not having permission for the command? if not, perhaps another perameter %o (over ride permission) could be added?
Thanks
@MrYellowKay
give the noobs the permission "bukkit.command.say"?
Also thanks for the updated plugin, this helps with people too lazy to learn commands!