Inactive [MISC] SupplySign - Infinite Item Distribution w/ Signs(chest/dispenser also supported)

Discussion in 'Inactive/Unsupported Plugins' started by redsgreens, Mar 10, 2011.

  1. Offline


    SupplySign is now on! Go there for the latest versions, a dedicated support forum, and ticket tracking system:

    SupplySign - Infinite Items Distribution via Signs (now with dispenser support!)

    Use this plugin to distribute items and blocks to your players by creating [Supply] signs that load a chest interface when right-clicked. These signs can also be placed on chests.


    The Basics:
    • Place a sign
    • Set the first line to [Supply]
    • On each of the remaining lines, put the name(or item id) of the contents of the supply sign
    • Right-click the sign to open the chest.
    Chest Sign: To place a sign on a chest, make sure it is not within one block of another chest. Place your supply sign on the ground next to the chest and it will attach itself to the chest after you are done editing the sign. Right-clicking the sign or the chest will display the contents of the sign. If you want, you can put two signs on a large chest.

    Dispensers: Attach a sign to a dispenser in the same way you would attach one to a sign. The inventory of the dispenser will always be full of whatever is on the sign. If you use a kit, or if you put multiple items on the sign, only the first will be used. Remember that dispensers require redstone to activate, so it might be a good idea to wire up the dispenser and test it before attaching the sign. If the dispenser doesn't work without a SupplySign on it, then I can't help you (I'm no redstone expert).

    Using Kits: To use a kit, set the first line to [Supply] as usual, then put "kit:" followed by the kit name on the second line, ie. "kit:wool".
    Default Kits: wool, dye, woodtools, woodplus, irontools, ironplus, diamondtool, diamondplus, goldtools, goldplus, desert, makecake, chainmail

    • Ops and players with the "supplysign.create" permission will be able to place supply signs.
    • Ops and players with the "supplysign.access" permission will be able to access them.
    • Ops and players with the "supplysign.destroy" permission can destroy existing supply signs.
    • Ops and players with the "supplysign.reload" permission can trigger a reload of items/kits data.
    • Players with "supplysign.access.kitname" can access the kit called "kitname".
    If you don't use permissions: Only Ops will be able to place SupplySigns. There is a config file option that will allow non-op players to access signs, but not place them.

    Data Files: After the plugin has been loaded for the first time, a "supplysign" data folder will be created in the bukkit plugins folder with two files in it: items.csv and kits.yml. You can customize these files to add new kits or modify item names. Use "/supplysign reload" to load your changes without restarting the server. NOTE: When editing these files, make sure the format doesn't change. On Windows, use something like Wordpad. There has been a report that OpenOffice can change the files in a way that breaks the plugin.

    Config File: Used to configure the ShowErrorsInClient, FixSignOnSignGlitch, and AllowNonOpAccess options. Check out the (automatically created) config.yml file for more info.

    This is an example of a SupplySign with a kit.

    And here is what you see when you right-click the sign in the previous screenshot.

    This is what a chest with a sign on it looks like.

    An arrow being fired from an infinite arrow dispenser. Watch out!

    This video gives an example of how to attach a SupplySign to a dispenser.​

    This plugin was originally based on the [Free] sign code from Essentials by Zenexer. Without his hard work there would be no SupplySign plugin. Thanks!
    Also thanks to vitaminmoo for testing this plugin and developing the kits.yml format.

    Old Changelog (open)

    Version 1.7.1 (08/09/2011)
    • Removed support for air blocks in signs (they break the game)
    • Corrected spelling of some items in items-base.csv
    • Replaced calls to deprecated Bukkit methods
    Version 1.7.0 (07/05/2011)
    • Added pistons and shears support
    • Access to SupplySigns on chests can now be protected by Lockette, WorldGuard, etc (allows finer grained access than previously possible)
    Version 1.6.3 (06/26/2011)
    • Added workaround for conflict with plugins that alter sign text color
    Version 1.6.2 (06/22/2011)
    • Fixed small bug related to custom items with a stack size less than the maximum for that item
    Version 1.6.1
    • The kit/item names are now case insensitive (suggested by Maxis010)
    Version 1.6
    • Replaced "items.csv" file with "items-base.csv" and "items-custom.csv" files to better handle new items added to Minecraft.
    • Added AllowNonOpAccess config file option (requested by Xiangliang2)
    Version 1.5
    • SupplySigns on dispensers now supported! (CB766 or higher required)
    Version 1.4
    • Fixed bug that prevented numeric item codes in kits.yml file (discovered by piousminion)
    • Added permission support for "supplysign.access.kitname" so you can restrict which kits a user/group can access (suggested by RaCooN)
    Version 1.3
    • Fixed bug where empty kits.yml file would break basic functionality.
    • Added support for large chests.
    Version 1.2
    • Fixed awful bug (discovered by Harushimo) that caused all signs in game to show an inventory. Oops.
    Version 1.1
    • Added new "supplysign.destroy" permission that can keep unauthorized players from destroying signs.
    • Updated to support Bukkit build 602. Servers running Bukkit 531/556 should still use version 1.0.
    Version 1.0
    • Added configurable option to hide client side error messages.
    • Fixed glitch where signs can be placed on other signs (can be disabled).
    • Config file support added.
    Version 0.9
    • Added support for signs on chests.
    Version 0.8
    • Added some diagnostic messages describing the number of items and kits loaded.
    • Fixed a typo in the items.csv file breaking birchwood and redwood. If you haven't customized your items.csv file, then just delete it and it will be recreated with the error corrected.
    Version 0.7
    • Initial release to the world.

    If you have problems: Check the diagnostic messages from SupplySign on the server console. You should see something like this when the plugin starts up, or when you use /supplysign reload :

    08:01:07 [INFO] SupplySign loaded 1092 items from items.csv.​
    08:01:07 [INFO] SupplySign loaded 16 kits from kits.yml.​

    If you see something like this:

    07:55:53 [INFO] SupplySign error: while parsing a flow sequence; expected ',' or ']', but got StreamEnd​
    07:55:53 [INFO] SupplySign loaded 1092 items from items.csv.​
    07:55:53 [INFO] SupplySign loaded 0 kits from kits.yml.​

    Then there is a typo in your kits.yml file and zero kits were loaded because of it. Unfortunately Yaml is a bit touchy about typos.

    If you can't figure out what's happening, post a capture of the SupplySign console output and attach your items.csv and kits.yml files to a your post so I can try and reproduce the problem. A screenshot of your sign could be useful as well.
  2. Offline


    Version 1.6.1 is out now that does exactly this. Thanks for the suggestion!
  3. Offline


    Can anyone tell me how to add halfblocks/slabs? I mean besides the smooth stone ones, like wood and cobble?
  4. Offline


    Here you go:
    • smooth stone: slab
    • sand stone: ssslab
    • wood plank: wpslab
    • cobble stone: csslab
  5. Offline


    Testing now.. It works and Its awesome!
  6. Offline


    I'm trying to figure out the custom file...
    I'm trying to add maps...
    I used the keyword "map" and "maps"
    I used the ID: 358
    I used damage: 0 (i'm not quite sure what the damage thing means lol)
    I used StackSize: 1

    I've reloaded the plugin. When I put the sign on the chest, nothing happens, it's just empty.
    Tho an error does pop up in the server window
    "SupplySign exception: Unknown item name: maps"

    Any suggestions? Is the items-custom.csv file working?
    Or could you add maps? :)
  7. Offline


    This worked fine for me. I added the following to my items-custom.csv file:
    HOWEVER, the reason I didn't add maps to the base csv file is that the actual crafting of a map plays into what it's "damage" value is, and what terrain is displayed on the map. If you add that line to your custom file, then everyone who grabs a map from that sign/chest will see a map centered on the sign/chest, or if people have been using maps on your server already, then they will get whatever was the first map created. Not very useful, in my opinion. Sorry if my explanation is not that great.. you can read more about it on the wiki.
  8. Can I make it so that, when players go out of this world and back to the Survival one, their items are removed? And vice versa.
  9. Offline


    The MultiInv plugin is designed to do that. I haven't tested it myself, though.
  10. Sorry, I got it to work thanks :D
  11. Offline


    Uber annoying bug!

    I'll create a SupplySign, (I.E. one with bows and arrows) it works fine. Turn my back for one moment, all the text on the sign turns blue. The sign is then empty. None of the contents are there.

    The only error I can find in the console is:

    14:55:55 [SEVERE] at redsgreens.SupplySign.SupplySignItems.getItem(
    14:55:55 [SEVERE] at redsgreens.SupplySign.SupplySignItems.showInventory(
    14:55:55 [SEVERE] at redsgreens.SupplySign.SupplySignPlayerListener.onPlayerInteract(
  12. Offline


    That's a weird one. Do you have any other sign-related plugins installed? What versions of SupplySign and Bukkit are you running?
  13. Offline


    I am using SpeedSign, SupplySign 1.6.2, and Bukkit recommended build #860.
  14. Offline


    There's a very good chance that this problem is due to a conflict with SpeedSign. If that plugin is changing the color of the lines after the first, then SupplySign won't recognize what's named on the sign. You might try removing SpeedSign temporarily to see if that fixes the problem. I'll try and test it as well, maybe there is a workaround I could come up with.

    UPDATE: This was definitely a conflict with SpeedSign. However, I was able to work around the issue, and I just released SupplySign 1.6.3 with this workaround included.
  15. Offline


    Ok i have essentials which gave me group manager so i added the permission to access the supply sign for default users but i get this error in game. [Essentialsprotect] Protection owner: zach
    Err: you do not have access to this SupplySign. :confused:

    please help me if you can and thank you in advance :)
  16. Offline


    Turn off EP for signs or Remove EssentialsProtect, there was a similar conflict with EP and Lockette, removing EP was the fix unless the user in question didn't disable EP correctly for signs
  17. Offline


    That got rid of the essential protect error but i still get 'Err: you do not have permission to access this SupplySign'
    PLEAE HELP ME!!!! lol :confused: oh and thank your for helping get rid of the essentials error.
  18. Offline


    I've never used GroupManager, but I am confident that SupplySign works fine with it. Make sure your players have "supplysign.access" permission.
  19. Offline


    ok i am still getting the error but worldguard is protecting that area but does that matter? because i added the permission to the default user profile and i still get 'Err: you do not have permission to access that supplysign' . thank you for helping me guys
  20. Offline


    WorldGuard is not the issue here, since SupplySign doesn't integrate with it. What you have is definitely an issue with permissions.
  21. Offline


    Assuming you are running permissions 3 use the command /pr username has supplysign.access.kitname
    Change username to a user you want to have access to a kit and kitname to that kit
    If permissions says you don't have access the kit then try checking things such as capitalisation in the kit file and the permission node
    If you DO have access to the kit by permissions but it's still rejecting you then grant yourself the global node supplysign.access and try again, I doubt this is the case but it's still something that should be covered to be sure
    Please post your findings
  22. Offline


    Running craftbukkit 935 and supply sign 1.6.3 I've tried to get pistons to work for a sign but they don't. I tried the name. I tried the item ID. Is this something wrong on my end?
  23. Offline


    Fairly soon there should be a new release that includes this information, but for now, add the text below to the end of your "items-custom.csv" file to add support for shears and pistons:
  24. Offline


    Thanks that worked!!!
  25. Offline


    i have group manager that came with essentials and i already added the permission node supplysign.access to the default profile in the groups file so that everyone can access it but default users still cant access it.
  26. Offline


    how come my sign won't generate maps?
  27. Offline


    Maps use the damage value to determine which instance of the map you are looking at, SupplySign will not be generating maps by default as all the maps would be damage 0
    This is an approx quote from the author the last time this was asked
  28. Offline


    Excellent work. This is an amazing plugin.
  29. Offline


    I've recently installed this plugin with permissions, but for some reason the signs won't hook onto the chest/dispenser.
    All of my other supply signs don't seem to work either. Any help?
  30. Offline


    I need more than "it doesn't work" to help figure out what's wrong.
    1. Do you get the SupplySign startup messages on the server console when the plugin loads?
    2. What happens when you try to make a SupplySign? Does the first line of text turn blue?
    3. What happens when you right-click a sign? Do you get an error in the client or on the server console?
  31. Offline


    in the next update will the supply signs support pistons? or am i doing something wrong?
    when i do that the chest is still empty

Share This Page