Bukkit

Better to stick with the last official (non yml) version at the moment I think. As long as you remember to do "/cmds save" every time you add some signs it should work perfectly. At least that's what I see here.

Still having an issue, it's happened twice now in the last 24 hours.

The size of the YML shrinks to 25% or less and the majority of the signs stop working.

This is after a restart.

Any updates? Cheers.

Use /cmds instead. That works.

Change the command for /cs update? It's already occupied by WorldEdit.

@zdb, is there an undocumented feature where "@<group>" is also found true if the user belongs to a permissions group of that name? I had a commandsigns.group.< groupname> perm, but also a PermissionsBukkit group with the same name. CommandSigns seemed to find "@<groupname>" true whether the user had the command signs perm OR the user was part of the PB group,with the same name.

One thought zdb, it would be good if the "!" only works if NOT OP. This way, OPs get max info for debugging. Of course you could use a permission to control this, but OPs should get all perms, including ignoring "!", regardless of perms.

Thanks, that would be great!

Is there anyway to stop chat messages from commands, in the same way ! works for group permission checks? As you've seen I do some permission changes when buttons are pressed that mean nothing to the user. It would be better if I could avoid confusing the user with these.

@zonedabone

It's very strange, and whenever the server restarts it is always the same 5-10 signs that reset now. Any word on that fix? Cheers

Zdb, did you see mine had a very similar ( to the uninformed eye) error on shutdown. See previous page.

I think that's the same thing I saw, on the previous page. I'm sure zdb is on the case.

@zdb. Thanks very much for taking the time to make that yml for me, but I've added,quite a few signs since the dat file I uploaded. So I'm going to wait for the next build before trying the yml version again. Hopefully that will be able to convert my old signs.

@zonedabone

On restart (this is your YML build)

java.lang.NullPointerException
        at org.zonedabone.commandsigns.CommandSigns.saveFile(CommandSigns.java:325)
        at org.zonedabone.commandsigns.CommandSigns.onDisable(CommandSigns.java:267)
        at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:217)
        at org.bukkit.plugin.java.JavaPluginLoader.disablePlugin(JavaPluginLoader.java:362)
        at org.bukkit.plugin.SimplePluginManager.disablePlugin(SimplePluginManager.java:399)
        at org.bukkit.plugin.SimplePluginManager.disablePlugins(SimplePluginManager.java:392)
        at org.bukkit.craftbukkit.CraftServer.disablePlugins(CraftServer.java:245)
        at net.minecraft.server.MinecraftServer.stop(MinecraftServer.java:399)
        at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:479)
        at net.minecraft.server.ThreadServerApplication.run(SourceFile:492)

That's fixed the redstone, thanks zdb!
It seems the sign worked first time until it got to the \message, then it was broken permanently. The sign would not work at all after that.

Zdb, is that just a problem with redstone or more generally?

Zdb, also having real probs trying to get redstone to work.

Still using your latest official version, none of the betas posted here. I get this most (but not all!) times the block is activated:

2012-05-12 09:52:15 [SEVERE] Exception in thread "Thread-47"
2012-05-12 09:52:15 [SEVERE] java.lang.NullPointerException
2012-05-12 09:52:15 [SEVERE] at org.zonedabone.commandsigns.CommandSignsClickHandler.runSign(CommandSignsClickHandler.java:237)
2012-05-12 09:52:15 [SEVERE] at org.zonedabone.commandsigns.CommandSignsEventListener$2.run(CommandSignsEventListener.java:84)

Bizarrely, sometimes it seems to work :confused:! Only a very small percent of the time though.