[MECH/EDIT] SimpleSignEdit v1.7.1 - Edit signs with right-click, now on BukkitDev [1060]

Discussion in 'Inactive/Unsupported Plugins' started by Celtic Minstrel, Mar 22, 2011.

  1. Offline

    Celtic Minstrel

    Not satisfied with the mechanics of other sign edit tools, such as requiring the use of commands, I went and threw together a plugin that lets you edit signs simply by right-clicking them with another sign in hand.
    Download from the BukkitDev page. (Older versions available here.)

    When you right-click to edit a sign, you can then view and edit the text of the sign just as you would when creating it. You can only edit signs if you are the owner or if they are owned by everyone. To include colours on the sign, use the & character followed by a digit or a letter from A to F. This works both when placing and when editing. If you want to include an & character on the sign, and the plugin interprets it as a colour code, simply double it and the plugin will realize that you don't want it to be converted.

    To see who owns a sign, hold a stick in your hand (you can change this to any item in the config file), and right-click the sign. To change who owns a sign if you have permission, hold a feather in your hand (you can change this to any item in the config file), and right-click the sign. Then either type the new owner name into chat, or walk over and punch them. You can also enter the symbols @, #, and * into chat to set the owner to yourself, no-one, or everyone, respectively. You could also edit ownership by editing the config file, but since signs are stored by their location that would not be an easy task.

    To configure the items used for setting/viewing the owner of the sign, simply set the "view-owner" or "set-owner" values in the config file to the ID of the item you want to use. You can also change the "allow-stacking" and "break-protect" values if you wish. It's probably a good idea to leave the "signs" section alone since that keeps track of who owns which sign. You can also configure it so that you need to be sneaking (or not sneaking) to edit signs.

    Permissions nodes:
    • simplesignedit.edit - Allows players to edit the signs they have placed as well as public signs (owned by everyone). If Permissions is not installed, everyone gets this.
    • simplesignedit.edit.all - Allows players to edit any sign, including those with no owner and those placed by others. If Permissions is not installed, only ops get this
    • simplesignedit.colour.<code> - Allows players to use the specified colour on signs. Available colours are listed here, but leave out the underscores and use all lowercase. Or you can just give simplesignedit.colour.*; also, the U in colour is optional. Currently this is restricted to ops if Permissions is not installed
    • simplesignedit.setowner - Allows players to change the owner of a sign. If Permissions is not installed, only ops get this.

    Config options:
    • allow-stacking - Allows sign posts to be built on top of sign posts; if false, an attempt to stack sign posts will result in the edit window appearing.
    • break-protect - Protect signs from being broken by people other than their owner. Obviously signs owned by everyone can then be broken by everyone.
    • orphaned-breakable - If the above is set to true, this controls whether signs owned by no-one can be broken by anyone.
    • sneaking - One of "true", "false", or "both"; if true, you must be sneaking to edit signs, and if false, you must not be sneaking to edit signs. The default, "both", means that your sneaking status is not checked when determining if you should edit the sign.
    • view-owner - The ID of the item used to see the owner of a sign by right-clicking. Defaults to stick.
    • set-owner - The ID of the item used to set the owner of a sign by right-clicking. Defaults to feather

    Video by Warby579:

    List of things to maybe do:
    • None right now


    Version 1.7
    • Now uses a database to keep track of sign ownership.
    • Added auto-save option.

    Version 1.6.2
    • Added configuration option to allow anyone to break signs that have no owner even if break protection is enabled; it has no effect if break protection is not enabled
    • Fixed a potential NullPointerException that would sometimes occur when disabling; this bug could in theory haved cause loss of owner data
    • Fixed PermissionsBukkit antibuild interfering with the operation of the plugin; now you should be able to edit signs if you have simplesignedit.edit even if you do not have permissions.build
    • Fixed duplication issue that resulted from a conflict with plugins that display an inventory window when right-clicking a sign; any other, similar duplication issues that I'm unaware of should be similarly fixed

    Version 1.6.1
    • Editing signs despite anti-build should now work with more anti-build plugins. It still might not work with some though.

    Version 1.6
    • Added an option to require that you are sneaking (or not sneaking) in order to edit signs. By default, you can edit signs regardless of whether you are sneaking.
    • Added the simplesignedit.* permission node, which somehow I managed to forget when implementing superperms support.
    • Added more API stuff. I suppose it's unlikely people will use it, but still. Also, the API is now used internally as well.
    • It should now be possible to make signs editable for users who do not have build permission. Whether it actually works may also depend on what plugin you use for anti-build. It still won't affect built-in spawn protection though.
    Taranis01, Pompeij and ksevelyar like this.
  2. Offline


    Here is my file. It appeared to me like it grew over time (by that I don't mean the signs list). The only entry I edited was "orphaned-breakable".
    config.yml (open)

    sneaking: both
    view-owner: 280
    set-owner: 288
    break-protect: true
    orphaned-breakable: true
    allow-stacking: true
    world(52,70,287): Nordic42
    world2(-396,87,-290): Nordic42

    Thanks. I now work with PermissionsBukkit. Everything works fine. And also thanks for the plugin, I like it very much. :)
  3. Offline

    Celtic Minstrel

    Settings aren't added until the plugin uses them; so, for example, if you don't enable break-protect you shouldn't ever see orphaned-breakable.
  4. Offline

    Don Redhorse

    but should the file be empty?
  5. Offline

    Celtic Minstrel

    The only way the file could be empty (or rather, contain just "{}") in the normal running of the plugin is if no-one ever builds signs or tries to edit them. And I'm not sure if it would be empty even then.
  6. Oh it will, it'S just having the {} indicating a list with null/nothing in it was written to it.
  7. Offline


    I'm having a lot of issues with this plugin, which is sad because it seems to have everything I need. We've got Permissions installed and I gave myself the 'simplesignedit.*' permission. Despite this, I can't change the owner of signs, can't use color on signs, and more or less can't do anything but edit the signs that are known to be owned by me. How do I fix any of these issues? Any info I could give you to help me out?
  8. Offline


    I had the same problem. The "Permissions" plugin is not supported by SimpleSignEdit (I think because Permissions is inactive) so the permissions default to OP. I guess you don't have OP status on your server.

    @Celtic Minstrel:
    I think it would be helpful, if you extend you first post by saying it is not compatible with Permissions, but compatible with the other permissions plugins.
  9. Which permissions system are you using?
  10. Offline


  11. it still could be 2.x or 3.x .....
  12. Offline



    I tested with 3.x and it did not work. So I think it is reasonable to assume the older version is incompatible too.
  13. Offline


    I am using Permissions 3.x right now.
  14. I've just taken a quick glance at the code. From what i've seen it supports the Built-In permission system now. This means each permission-plugin supporting it should work with SimpleSignEdit.
    And Permissions 2.x/3.x do not AFAIK.
  15. Offline


    ): Dang. Sad for me, I suppose. Thank you for letting me know! You think it's worth the effort for me to look into using the built in permissions, then?
  16. Well it definitly is, at least i do think so, it is native for every Bukkit Server and most plugins support it already.
    I wold make a list of Plugins i use and check which of them support it and which not and search for alternatives.
  17. Offline

    Celtic Minstrel

    @TheDeejay – Neither Permissions 2 nor Permissions 3 are supported now; if you want to switch to a permissions plugin supporting the built-in permissions, I believe PermissionsEx would be the simplest choice since it uses pretty much the same config file format. Your other options that I am aware of are PermissionsBukkit and bPermissions.
  18. Offline


    With PermissionsBukkit you can use SuperpermsBridge. It provides downward compatibility to the old permissions system and works perfectly fine.
  19. True, but does not work with ALL plugins :(
    Had a very old one and the bridge wasn't able to communicate with the plugin (don't ask which plugin it was i've deleted it and can't remember
  20. Offline


    Hey, I love the plugin but I do have one concern. I'm having a problem with sign text disappearing. I have permissions installed and working, and if someone without authorization to edit or remove a sign tries to destroy it, the sign stays but the text on the sign disappears. Any ideas why this would happen???
  21. Offline

    Celtic Minstrel

    @SenorHoward – I suspect that may be a client-side glitch (though it may be one I can fix server-side). Does the text return if you log out and back in, or if someone with authorization to edit tries doing so?
  22. Offline


    Ok, I tried to stop the server and reload into the game and all the text came back. It's just a single instance sort of glitch I suppose. If an unauthorized player tries to break a sign owned by someone else, the text disappears until the next load. Glad to know it isn't actually broken though!
  23. Offline

    Celtic Minstrel

    Um, simply logging out without shutting the server down and then logging back in isn't enough to fix it? It should be, at least.
  24. Offline



    I use the Essential GroupManager 1060, and the permissions do not work here.

    can you fix it?
  25. Offline

    Celtic Minstrel

    No. Essentials GroupManager is not supported and will never be supported.

    You can try using SuperpermsBridge, though; you can find it as an extra download in the PermissionsBukkit thread. If you install that along with GroupManager, this might work. No promises though, and if it doesn't work then you're just out of luck.
  26. Offline


    You are quite right, lol. Thanks!

    Superpermsbridge is a good one, but I'm personally using PermissionsEx. It's nice because if you don't want to mess with the yml files, you can set all of your users, groups, and permissions either through your server console or through in-game commands

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: May 13, 2016
  27. Offline


    hey i have give my mods the simplesignedit.colour.* permission but they can't use color codes on the signs !? :confused: for me works the colorcodes, iam admin with * permission, is maybe the simplesignedit permission wrong ?
  28. Offline

    Celtic Minstrel

    What version?
  29. any chance that SimpleSignEdit will start logging all the signs in MySql database insteed of the config file?
  30. Offline

    Celtic Minstrel

    I have considered switching to a database, but I probably wouldn't bother with explicit MySQL support; I'd either be directly using SQLite, or using the eBeans persistence engine (and thus supporting all databases that it supports).
  31. On CB 1060 The plugin loads, color signs work, I'm set to owner, but right clicking the sign doesn't do anything.
    This is with spoutcraft.

    Confirmed with 0 plugins, and me as OP.

Share This Page