Bukkit

@Dibujaron

Instead of

/cs line0 use /cmds line0

The one with the dispenser you can do yourself...

Make a sign:

/cmds line0 (this is a safety line so its always possible to add afterwards)

/cmds line1 $1

/cmds line2 /^region select dispenser

/cmds line3 /^/set redstonetorch

/cmds line4 %2

/cmds line5 /^/set 0

Then you make a dispenser and define the block behind it as dispenser with worldedit.. every time you click the sign a redstonetorch will spawn behind it a trigger the dispenser

Regards Unplugged

I need help: So I'm trying to make signs that elevate your permissions in order to run commands that players normally couldn't do, like "/gamemode" and I made the sign with "/*gamemode", but whenever anyone tries to use it, it doesn't work, and just gives this error in console:

[WARNING] Task of 'CommandSigns' generated an exception java.lang.NullPointerException at org.zonedabone.commandsigns.CommandSignsClickHandler$RunHandler.run(CommandSignsClickHandler.java:341) at org.bukkit.craftbukkit.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:126) at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:533) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:459) at net.minecraft.server.ThreadServerApplication.run(SourceFile:492)

PLEASE HELP ME!

Hey Zone.. :D Still love your cmd signs man! they work great. .:D!

Any idea when the "chance/random/percent" will be ready

+

will you be makin it possible for a sign to be used only 1 time per player

@MKindy

The /# seems to have worked, thank you so much for taking the time to reply, I will have a look at the permissions just out of curiosity, but I'm glad it's working now.

@stevevbrewer

You have your syntax right the first time for making the commandsign. '/cmds line0 /*manuadd <name> citizen' should work if the node 'groupmanager.manuadd' is added to CommandSigns' entry in Bukkit's permission.yml file. I would expect '/cmds line0 /^manuadd <name> citizen' to always work, as it should give temporary Vanilla OP to the player clicking the sign and executing that command. You could try making CommandSigns run the command from the console, with '/cmds line0 /#manuadd <name> citizen'.

I'm not familiar with Essentials/GroupManager, but a thought occurs to me that there could be a setting for it causing interference... when you change player groups yourself, do you do it in-game or via the console? I'm just wondering if there is a setting that prevents vanilla OP from inheriting the 'groupmanager.*' permission, which would explain why the /^ command doesn't work - you could test this by stripping someone of their 'groupmanager.<etc>' permissions, then OPping them and having them try to use the /manuadd command manually; and if the permission node 'groupmanager.manuadd' isn't in CommandSigns' entry in permission.yml, that will explain why the /* command doesn't work. Either way, I fully expect the /# command to work with no changes on your part, but if you want to dive deeper it's worth exploring your settings.

is there a better way for command signs to run commands as if it was done by the player when down via redstone? want to do a few essential commands weather, smite time  im having trouble to work via redstone even with /^ because it is world and player specif commands

@MKindy

I'm not sure what you mean. I tried all of these:

<<code>>/cmds line0 /*manuadd <name> citizen

/cmds line0 /^manuadd <name> citizen<</code>>

Both gave me wrong syntax error

<<code>>/*cmds line0 /*manuadd <name> citizen

/^cmds line0 /*manuadd <name> citizen<</code>>

Commands don't exist

I guess I could use ThumbsApply and just make the command enter the password for them but I was kind of hoping to allow signs to promote players and generally do things for them without giving them permission to do it whenever they want, where ever they want and in some cases to whoever they want.

@stevevbrewer

Even if they have commandsigns.use.*, they also need to have permission for the specific command you are trying to run; elsewise you need to run the command with elevated permissions via the commandsign, by using /*<command> or /^<command> as appropriate.

@Qentus

Oh right, that's what I meant. My bad.

@MKindy

Thanks. It isn´t "/qm channel text" but I searched a while and I found "/ch qm channel text".

I'm using GroupManager (plugins listed here) and although my players have commandsigns.use.* they don't have access to the command the sign is running for them:

@Qentus

Hey Qentus, check the documentation for the chat channel plugin you use. Channel shortcuts usually won't work, in my experience; however, the plugin I use, Herochat, has a "quickmessage" command, /qm; hence, in Commandsigns, the command would be formatted like "/qm g <text>" to send "<text>" to channel 'g', in my server's case, the General channel.

Also note, this will provide the chat plugin with the name of the person who activated the sign. If the sign is redstone activated, your chat plugin will need to support commands run from the Console.