SignEditor
SignEditor does what it says on the tin: allows you to edit your signs!
SignEditor can allow everyone to edit any signs they have access to!
Use:
To edit a sign, aim at the sign and type in:
/edit [line] [Text]
Example:
/edit 1 Hello
Results in the first line of the sign changing to hello.
You can also copy and paste entire signs with the copy and paste commands:
/edit copy /edit paste
Important Note
Sign Editor calls BlockBreak, BlockPlace and SignChange events for every command executed. This means that any plugins that control placement or breaking of signs will have priority. For example, LogBlock will track all edits and WorldGuard can prevent changes. So can plugins like Lockette and ChestShop.
Permissions
se.edit (Default: op)
This is the basic permission node, needed to edit any signs. Granting this allows users to edit any sign they can.
se.editCol (Default: op)
This allows players to add colours to their signs.
Colours are added with the & followed by a colour code. &s can be entered by using the escape character \ (\&). \ can be entered by escaping a \ (
)
se.force (Default: op)
This permission node allows the player to force BlockBreak, BlockPlace and SignChange events to succeed even if another plugin cancels or modifies it. In order to use this, you must add an exclamation mark after the line number, i.e.:
/edit 2! lemons
You will get notified of any bypasses that are made.
se.dforce (Default: false)
This permission node allows you to skip the bukkit events entirely, allowing a change to a sign that would otherwise be blocked or cause it to break. This is useful when the force option still doesn't work.
The problem with a Double Force is that plugins do not receive any of the events, so if you have any plugins that rely on those things (i.e. LogBlock) then they will not work! Conversely, it can be used to bypass the limitations some plugins put in place.
To enact a Double Force you must have both the force and dforce permissions and you put two exclamation marks after the number, i.e.
/edit 2!! lemons
Video Example
Thanks to VariationVault for this video:
@meiamsome Hmm, I dont think its your plugin at fault, I tried reseting minecraft, and now colours show up if I look at the sign from the side, but still none if I look directly at it...
@Melonking
That's odd. What exactly do you type?
Great plugin, one of the most useful on my server! :D
That was my first guess too, however I am getting the same thing if I am op'd and SignEditor is the only plugin in the plugins folder, and this is happening on my laptop and server, both with bukkit 2735, no errors.
@Melonking
Is there an error log?
Have you checked you have the se.editCol permission?
I can only assume that it is an external plugin that allows you to add colours that you don't have permissions for correctly, can you check that?
It works for me when I try it with the latest version.
Hmm, I type a color code like &3Text and the &3 vanishes, but the text remains black :(
@kgame
Added in 1.01 :D
Can TODO onTabComplete when type "/edit 1 " then press Tab key.
Will auto read exist line 1 text.
@yuk75
It means that some plugin is not letting SignEditor destroy the sign in your name. Can you confirm you can destroy it with your hand?
It keeps telling me sign break is blocked by plugin, but the sign is already broken :(.
It's an essentials buy sign, I'm an op, Essentials perms are all correct and everyone has editing perms so what's this mean? :(
someday when mojang aren't fully retarded we will be able to once again edit signs the easy way.. like this plugin allowed, before those idiots at mojang broke it again.
http://dev.bukkit.org/server-mods/simplesignedit/
@meiamsome
That's an even better idea. Good work!
@McJellyGooby
No, I simply removed the LogBlock integration.
Now basically what it does is call the Bukkit events for Destroying, Creating and Editing the sign. Therefor, LogBlock will log it all very well, WorldGuard can block it all and etc.
@meiamsome
Don't feel bad, chum. Calling logblock for sign ownership is a perfectly good idea. The problem was that it's difficult to properly execute it, possibly due to some quirks in LogBlock itself. Am I correct in assuming you've adopted the Worldguard model I proposed the other night?
@FluffyTheNeko
@McJellyGooby
Yes, this is correct - The bugs in the old version outweighed any usefulness keeping them had. They were bad and I should (and do) feel bad.
@FluffyTheNeko I believe he removed the old versions because of a flaw in the Logblock dependency. When we were testing the plugin, I suggested an alternative method to regulate sign editing, which would be simpler than calling on LogBlock. I believe he is using that method now.
Why did you remove all the old versions?
@zeiroe
Thanks for pointing out the flaw! :P
@Lazor_16
I have been able to use this plugin with ServerSigns and ChestShop, no problems. I was even able to modify a ChestShop sign to correct an item being sold without having to recreate the sign. Awesome plugin! Thanks for the chained colorcode update meiamsome!
@Lazor_16
I have no idea, sorry.