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

    redsgreens

    SupplySign is now on dev.bukkit.org! Go there for the latest versions, a dedicated support forum, and ticket tracking system: http://dev.bukkit.org/server-mods/supplysign/

    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.

    Download: http://dev.bukkit.org/server-mods/supplysign/

    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

    Permissions:
    • 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.

    Screenshots:
    example-using-kit.png
    This is an example of a SupplySign with a kit.

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

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

    2011-05-09_15.52.15.png
    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.​

    Thanks:
    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. ok thx i will try it later see you soon :D
     
  3. Offline

    STiChad

    Yeah I ran into a problem with Permissions
    I want certain groups to have access to certain supply signs and only those signs.
    Code:
            - -supplysign.access.diamondplus
    Does not work, all groups can still access it.
    Am I doing it wrong?
     
  4. Offline

    Maxis010

    Try having this
    - supplysign.access.*
    - -supplysign.access.diamondplus

    The difference being is supplysign.access grants the node "access" while supplysign.access.* grants all the subnodes of access but not access itself
     
  5. Offline

    redsgreens

    What @Maxis010 suggested is a good idea. Keep in mind that "supplysign.access" permission by itself supersedes any "supplysign.access.kitname" permissions(positive or negative).

    An alternative would be to list the kits that each group should have access to, instead of giving access to all and then removing ones they shouldn't. Like this:
    - supplysign.access.kit1
    - supplysign.access.kit2
    - supplysign.access.kit3
     
  6. Offline

    STiChad

    Ok I'll try both. I thought doing
    - supplysign.access.kit1
    - supplysign.access.kit2
    - supplysign.access.kit3
    Would still give them access to others as well.
    I will try both and see what happens.
    EDIT: Damn, they both didn't work.
    I did
    - supplysign.access.*
    - -supplysign.access.diamondplus
    and
    - supplysign.access.kit1
    - supplysign.access.kit2
    - supplysign.access.kit3
    (But with the proper kits)
    And still no luck.
     
  7. Offline

    redsgreens

    @STiChad: can you describe more precisely what you are trying to accomplish? I'd like to test this myself, but I'm not 100% clear on what your goal is.
     
  8. Offline

    STiChad

    Alright I want to be able to give the group "Builders" access to the ironplus kit but not the diamondplus or chainmail.
    When they sign up for Premium their group will change to "Premium" and they will have access to all of it.
    See where I'm goin?
     
  9. Offline

    redsgreens

    Here is the groups section of a permissions file that will accomplish that:
    Code:
    groups:
        Default:
            default: true
            info:
                prefix: ''
                suffix: ''
                build: true
            inheritance:
            permissions:
        Builders:
            default: false
            info:
                prefix: ''
                suffix: ''
                build: true
            inheritance:
                - Default
            permissions:
                - 'supplysign.access.ironplus'
        Premium:
            default: false
            info:
                prefix: ''
                suffix: ''
                build: true
            inheritance:
                - Builders
            permissions:
                - 'supplysign.access'
        Admins:
            default: false
            info:
                prefix: ''
                suffix: ''
                build: true
            inheritance:
            permissions:
                - '*'
    
    If you want the Builders group to have access to more kits, add more lines, one for each kit that they should have access to.
     
  10. Offline

    STiChad

    Gah, still doesn't work.
    They still have access to all of them.
    I did exactly like you did and Builders still have access to them all.
     
  11. Offline

    matttman8910

    Cocoa bean problem, please help.
     
  12. Offline

    redsgreens

    Use "cocobeans" or "cbeans"
     
  13. reds not work..
    I try it but he says no permissions....
     
  14. Offline

    OZ4RK

    I'm doing everything correctly but the sign won't respond in any way. It won't dispense items. It won't work on chests either. I did encounter this error:

    Code:
    16:12:14 [INFO] SupplySign loaded 2 config parameters from config.yml.
    16:12:14 [INFO] SupplySign loaded 1108 items from items.csv.
    16:12:14 [INFO] SupplySign loaded 13 kits from kits.yml.
    16:12:14 [SEVERE] BLOCK_DISPENSE loading SupplySign v1.5 (Is it up to date?)
    java.lang.NoSuchFieldError: BLOCK_DISPENSE
     
  15. Offline

    redsgreens

    My suspicion is that you are running a CraftBukkit build lower than 766. If so, you should be running SupplySign version 1.4(no dispenser support).
     
  16. Offline

    kyneflaretail

    alright, i'm having a problem, i'm using group manageer, and have the node typed in correctly to give erveryone access to the chests/dispensers, but only ops can access the dispensers i've got set up, and even the admin, when un oped, can't access the dispensers, but everyone can access chests.

    the setup i use for the dispensers is:

    dispenser w/sign
    RS torch
    block w/button

    any help?
     
  17. Offline

    redsgreens

    No one(op or not) should be able to right-click on a dispenser with a SupplySign to access it's inventory directly. The SupplySign will keep the dispenser full of whatever item is on the sign, and the only way to get items out of the dispenser is to power it with redstone. Does the dispenser work as expected without the SupplySign attached?
     
  18. Offline

    kyneflaretail

    yes, the dispenser works without a sign, and i meant that pressing the button beneath it only owkred for the ops when everyone should be able to do so, sorry should have been clearer on that n.n"
     
  19. Offline

    redsgreens

    Are you using WorldGuard or something along those lines? SupplySign does no checks on how a dispenser is powered, so there must be something else going on.
     
  20. Offline

    Elfsovereign

    Hey I'm having a problem using my kits in conjunction with SupplySign. Here's the code for my kits:
    Code:
    #
    # This is the default kit file for CommandBook.
    #
    # Each kit requires the commandbook.kit.[name] permission, such as:
    # commandbook.kit.starter (as seen below).
    #
    # The name of the items are names that you can use with the /item command,
    # so you can do step:wood if you want. If you want to specify an amount, enter
    # the number after a comma, like "wood,64".
    #
    [starter]
    ironpick
    ironaxe
    ironshovel
    wood64
    torch,64
    [admin]
    diamondpick
    diamondaxe
    diamondshovel
    diamondsword
    log,64
    stone,64
    glass,64
    torch,64
    glowstone,64
    310
    311
    312
    313
    271
    345
    string
    [wool]
    35:0,64
    35:1,64
    35:2,64
    35:3,64
    35:4,64
    35:5,64
    35:6,64
    35:7,64
    35:8,64
    35:9,64
    35:10,64
    35:11,64
    35:12,64
    35:13,64
    35:14,64
    35:15,64
    [electric]
    331,64
    331,64
    331,64
    331,64
    331,64
    356,64
    356,64
    76,64
    76,64
    1,64
    1.64
    69,64
    69,64
    77,64
    77,64
    70,64
    70,64
    72,64
    72,64
    [build]
    1,64
    1,64
    1,64
    4,64
    4,64
    4,64
    48,64
    48,64
    17:0,64
    17:1,64
    17:2,64
    20,64
    20,64
    3,64
    3,64
    24,64
    24,64
    45,64
    45,64
    13,64
    [sheep]
    351:0,64
    351:1,64
    351:2,64
    351:3,64
    351:4,64
    351:5,64
    351:6,64
    351:7,64
    351:8,64
    351:9,64
    351:10,64
    351:11,64
    351:12,64
    351:13,64
    351:14,64
    351:15,64
    [food]
    297,64
    297,64
    297,64
    297,64
    260,64
    260,64
    260,64
    282,64
    282,64
    282,64
    357,64
    357,64
    357,64
    349,64
    350,64
    319,64
    320,64
    322
    335
    354
    338,64
    295,64
    [furniture]
    44:0,64
    44:1,64
    44:2,64
    44:3,64
    58,64
    61,64
    54,64
    53,64
    67,64
    47,64
    50,64
    25,64
    23,64
    84,64
    85,64
    91,64
    282,64
    321,64
    324,64
    330,64
    6:0,64
    6:1,64
    6:2,64
    64,64
    [rare]
    46,64
    49,64
    87,64
    88,64
    59,64
    2256,64
    2257,64
    346,64
    337,64
    302,64
    303,64
    304,64
    305,64
    348,64
    81,64
    30,64
    ice,64
    18,64
    [tools]
    256
    257
    258
    259
    261
    262,64
    267
    268
    269
    270
    271
    272
    273
    274
    275
    283
    284
    285
    286
    290
    291
    292
    294
    298
    299
    300
    301
    306
    307
    308
    309
    314
    315
    316
    317
    345
    347
    [transport]
    66,64
    66,64
    66,64
    66,64
    27,64
    28,64
    331,64
    76,64
    333,64
    328,64
    329,64
    342,64
    343,64
    Where have I gone wrong here?
    It gives me an error report in game of 'err. unknown kitname'
     
  21. Offline

    kyneflaretail

    it is within the spawn protected area, so that may be the problem, i'll check that, if no luck i'll letcha know
     
  22. Offline

    redsgreens

    The text "This is the default kit file for CommandBook." tells me that you are editing the wrong kit file. SupplySign has it's own "kits.yml" file in the "/plugins/supplysign/" folder. Unfortunately, the kits used by CommandBook cannot be shared with SupplySign.
     
  23. Offline

    Elfsovereign

    Yep I saw that after tinkering with it. I mostly have it working now. Do you think you could incorporate the colon settings with items in a future update? People coming from commandbook are just comfortable classifying which log one means with a colon and a number, i.g. 17:0, 17:1, 17:2 for the three differing log types. This messed me up for quite a while with the yaml, and I just settled for the one type of wood, and the three saplings x.x
     
  24. Offline

    kyneflaretail

    Well, found out that it is indeed the spawn protection that's causing the setup to not work. well damn, know any way around this besides turning down the spawn protection area?
     
  25. Offline

    Xiangliang2

    When I place a sign only my Ops can access its contents. Can I make it so anyone can access them? I don't have permissions.
     
  26. Offline

    redsgreens

    A permissions plugin is currently required to allow access to non-ops.
     
  27. Offline

    Xiangliang2

    Awww :(

    Is it possible for you to add a setting in the config file. One which toggles whether or not only ops can use the signs?

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

    redsgreens

    That's definitely doable. I've got some other changes I'm working on with this plugin, so a release should be out in the relatively near future.
     
  29. Offline

    redsgreens

    SupplySign version 1.6 is out with the following changes:
    • 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)
     
  30. Offline

    Maxis010

    this is a Feature Request/Bugfix
    When checking for names can you have the plugin read the name to a string, then convert that string to lowercase THEN check for a matching item, myself and a number of my admins have to rebuild our signs because we caps a letter by force of habit, this would counter act this problem and would make the plugin more user friendly
     
  31. Offline

    weepingboil

    When I set AllowNonOpAccess to Yes, and a nonop clicks a sign, the sign rotates! (I guess this is by design?)

    Can you possible add an option to turn this off? (I'm getting lots of confused players!)

    Edit: Strike that - not your plugin after all!
     

Share This Page