Inactive [SEC/MECH/ECON] Residence v2.4.2 - Self serve area protection system! Buy/Sell Land! Economy! [1185]

Discussion in 'Inactive/Unsupported Plugins' started by bekvon, Mar 21, 2011.

Thread Status:
Not open for further replies.
  1. Offline



    v2.4.2 Released - 9/24/2011​
    See the change log for details.​
    Everyone using PermissionsEx, Essentials, or anything else besides the regular permissions plugin or PermissionsBukkit should add or change this in their config under the Global section:
    LegacyPermissions: true
    As of 2.4.0 the bPermissions plugin is supported directly.​
    As of 2.3.7 the PermissionsBukkit plugin is supported directly.​
    This support is not done through the new built in Permissions that bukkit provides, because there is no way to get a players group using the built in methods. However, by supporting this directly, you can now use the new permissions system while still keeping Residence, and not having to use old permissions at all anymore.​

    Latest Recommended Build
    Version: v2.4.2
    Download: Residence

    Latest Development Build
    Latest Snapshot: Residence.jar
    Latest Config: config.yml

    Developer API: Wiki
    GitHub Source: GitHub
    DevBukkit Project Page: DevBukkit


    Daniel Few (Wiki)​
    Linaks (Residence Logo)​
    SirHedgehog (Code)
    GSValore (Code)​
    Samkio (Wiki Video)​
    JustinGuy (Code)​

    Residence Signs (by KarnEdge)​

    NOTE: All Residence usage information has been moved to the wiki!

    Residence is different from most protection plugins in that it aims for the users to be able to protect their own homes without having to bother the admin to do it. Residence has support for a variety of different protection types including preventing movement through areas, all of which can be configured by the land owner, and limited by the admin.​
    Features (open)

    • Allows players to define protected areas for themselves.
    • Individual permissions for each protected area. Land owner can give / deny permissions globally or to other specific players.
    • Different permissions per land include: move, build, use, pvp, fire, teleport, monsters spawn, damage prevention
    • Support for group permissions on protections.
    • Multi-World support.
    • Teleport system to allow users to teleport to residences.
    • Collision detection system to prevent residences from overlapping.
    • Limits to protected size can be set up by the admin.
    • Limits to number of protected areas per player can be set.
    • Two ways to select land including using the select command, or using a item to select 2 points.
    • Messages when you enter / leave a residence. (customizable)
    • Land "leasing" system which requires users to renew the lease on their protection every X number of days or loose the protection. (off by default, see config file)
    • Recursive Sub-zoning. Create zones within zones, and then zones within those zones...
    • TONS of configuration for admins. Customize every single flag that players can or cannot use in the config file, based on their permissions group.
    • (Optional) IConomy support, can set up cost per X number of blocks protected.
    • (Optional) Permissions support.
    • In-game help / commands descriptions

    • Fix bug affecting some people with the new save system
    • Support for iConomy 6
    • Prevent enderman from messing with blocks in residences with the -build flag.
    • Paintings are now protected properly (Thanks JustinGuy!)
    • Fix Rent auto-renew bug.
    • Fix other miscellaneous small bugs.
    ChangeLog (open)

    • Support for bPermissions
    • Add "/res pset <residence> [player] removeall" command to remove all flags for that player
    • Added console only command "/resworld remove [world]" to remove all residences in a world.
    • "/res remove" now requires confirmation using the "/res confirm" command, before removing a residence.
    • Fixed subzone flag.
    • Fixed a few null pointer exceptions related to the "/res message" command, and a few other issues with it as well.
    • Fixed few cosmetic rent message bugs.
    • Fixed few mispellings...
    - Added name filter to Residences to prevent characters that mess up YML from being used. This should fix many of the errored YML files that people have been getting.
    - Fixed arrow damage in no-pvp zones (bug introduced in the Residence 1060 update).
    - Added a "Permissions Group" line of text into /res limits, this will show your Permissions group as reported by Residence.

    - Fixes to better handle the piston flag, and world "flow" flags (thx JustinGuy :) )
    - "Use" flag now covers trap doors.
    - Lease renewal can now be pulled from the Residence's bank.
    - Buying a residence now causes the default flags to be set for the user who is buying it.
    - Minor fixes to new PermissionsBukkit support (fix message about permissions not being detected when it actually was)
    - Added a few miscellaneous forgotten commands to the in-game Residence help.

    • Added direct support for PermissionsBukkit (doesn't go through the bukkit API)
    • Added LegacyPermissions true/false config option.
    • Support for residence.admin and residence.create permission nodes using new permission system.
    • Recommend using SuperPermsBridge or something that ensures backwards compatibility with old permissions.
    • Few permission changes to hopefully make it work better.
    • Fix for firespread flag with CB1000.
    • Added "piston" flag.
    • Fixes for CB1000
    • Fixes for a few minor bugs, and for concurrent modification issue with the Lease Manager.
    • Removed subzone list from /res info, and gave it its own command that supports multiple pages, /res sublist <residence> <page>
    • If the save file errors, it will now be preserved rather then overwritten, it will be renamed res-ERRORED.yml, the plugin will now disable itself upon error as well unless the StopOnSaveFault option in the config is set to false.
    • Fixed non-working per-world flags.
    • Fixed a few message bugs.
    • Add /resadmin removeall <player> admin command to remove all residences owned by a player.
    • Changed MaxUpDown in the default config to 128...
    • Fixed issue with /res vert still selecting more then the MaxUpDown allowed.
    • Fixed a few initial issues with a couple language localization messages.
    • Removed area list from /res info, use /res area list [residence] or /res area listall [residence] now.
    • New language localization system, upon first run v2.3 will create a Languages folder under your Residence config folder with the default English.yml file.
    • New in-game help system. (part of the new language localization system)
    • All commands now run without admin privileges unless you specify /resadmin before.
    • Added config option to allow rented residences to be modifiable. (PreventRentModify option)
    • Fixes to improve compatibility with Permissions 3.X
    • /res listall now has pages
    • Added the "physics" flag to control block movement. (separated from the flow flag more like)
    • New ResidenceTPEvent, and ResidenceRentEvent API events
    • Fixed residences not being properly removed from lease / rent system, upon deletion.
    • Fixed bug related to default group option in the config.
    • Fixed global "container" flag bug.
    • Fixed some NPE's related to explosions.
    • Added /resload command to load the save file after you make changes to it (UNSAFE, as it does not save residences first, and so you may loose new residences that were just created)
    • Added per residence Blacklist/Ignorelists that will allow you to specify certain block types to be ignored from residence protections, or unable to be placed in residences.
    • Added Server owned land, use /resadmin server <residence> to change the owner to "Server Owned"
    • Added global Ignorelists which allow certain block types to become unprotectable for the whole world / for a specific user group.
    • Fixed a couple bugs with the lease system, including being enabled when it shouldn't be and the lease auto-renew option.
    • Added "/res area replace" command, allows you to resize / move a physical area. If the new area is bigger, it will only charge you for the difference in size.
    • Added 'waterflow' and 'lavaflow' flags which override the flow flag if set.
    • Fixed a bug causing money to still be charged when failing to add a area to a residence.
    • Fix case sensitivity bug in rent system.
    • BOSEconomy support.
    • Essentials Economy support.
    • RealShop Economy support.
    • Added the 'place' and 'destroy' flags, which if used overrule the 'build' flag. These allow you to give only block placement permissions in a certain area, or only block destroy permissions.
    • /res check [residence] [flag] <player> command, this command evaluates if <player> is affected by [flag] at [residence]. You can leave off <player> and it will use your name.
    • Added a LeaseAutoRenew config option, that will cause leases to automatically renew so long as the player has the money to do so. Note that, if economy is disabled this doesn't work, as there would be no point to leases. Needs Testing! :)
    • Global FlagPermission config section, that allows you to give permission to use a flag to all groups, useful for the build / move / use flag that you almost definitely want everyone to have access to. Flags under each individual group will overrule these.
    • You can now set a limits on how deep or how high protections can go into the group, using each groups MinHeight and MaxHeight settings.
    • /res select sky, and /res select bedrock commands, these auto adjust to the above mentioned MinHeight and MaxHeight settings, so it won't select into a area you can't protect.
    • Rent system implemented.
    • Many bug fixes, including proper creeper explosion prevention now. Also, fixed some bugs when renaming residences.
    • New healing flag.
    • The monsters flag has been split up into "animals" and "monsters" now.
    • New Developer API, including custom Bukkit events.
    • New Global CreatorDefault / GroupDefault / ResidenceDefault flag sections to help clean up the Groups section, and remove redundant flags.
    • Probably some other minor things I've forgot :)
    - Residence 2.0 now in alpha testing, core code has been mostly rewritten.​
    - Supports multiple areas per residence using '/res area <add/remove>' commands.​
    - Added new selection commands '/res select expand' and '/res select shift'​
    - Added Predefined permission lists that can be applyed to residences.​
    - Enter / Leave messages now support %player, %owner and %area variables.​
    - Config file has been cleaned up and most things are better named.​
    - Should be fixed to work with newer iConomy versions.​
    - Save system now only uses yml as save format.​
    - Save system wont corrupt the whole file if one residences gets corrupted, you just loose that one residence.​
    - When a residence changes owner, flags are set to default for that owner.​
    - Added '/res default' command to manually reset flags to default.​
    - Released source code for v2.0​

    v1.2.8 - BETA
    - Fixed broken flag setting permissions.​

    v1.2.7 - BETA
    - Fixed chests being able to be opened from outside protected area.​
    - Fixed enter/leave message (hopefully)​
    v1.2.6 - BETA
    - Updated for CB 612 / Minecraft 1.4​
    v1.2.5 - BETA
    - Fixed tiny bug in saving messages.​
    - yml is now the default save format because its more reliable.​

    v1.2.4 - BETA
    - Fixed bug related to fire / ignite event.​
    - Added ability to remove enter / leave messages​

    v1.2.3 - BETA
    - Added a optional different save system, you can now save residences in pure YML format (same format as config files). See the config file for how to enable.​

    v1.2.2 - BETA
    - Fixed TP bug.​

    v1.2.1 - BETA
    - Fixed bug in new saving system.​

    v1.2 - BETA
    - New save system, will attempt to auto-convert from old system.
    - Fixed some permission bugs when not using permissions plugin.​
    - OPs are now residence admins when not using permissions.​
    - Fixed collisions detection issues related to having multiple worlds.​
    - Added global pvp setting.​
    - Added a "flow" flag to control water/lava flow in residences.​
    v1.1.9 - BETA
    - Fixed a severe bug when not using permissions.​

    v1.1.8 - BETA
    - Fixed a subzone bug.​
    v1.1.7 - BETA
    - Added ability to buy and sell land using /res market commands.​
    - Added a land leasing system which can be configured to expire protections if they are not renewed after a period of time. See the /res lease command. (this is off by default, turn it on and customize it in the config)​
    - Implemented a Auto-Save interval. Saves residence areas every X minutes.​
    - Fixed minor onBlockIgnite error.​
    - Added a few admins commands using /resadmin.​

    v1.1.6 - BETA
    - Fixed spaces not working in enter / leave messages.​

    v1.1.5 - BETA
    - Added Enter / Leave messages for Residences, as well as a permission option in the config to allow / deny changing of them.​
    - Fixed residence admins not being able to modify the outside world when using deny build rights outside of residences.​
    - Fixed issue related to default group.​
    - Added a config option to specify the default group.​

    v1.1.4 - BETA
    - Fixed bug in group permissions...​
    v1.1.3 - BETA
    - Changed the configuration vastly again, server admins now have control over every flag for every group.​
    - Group permissions implemented, but in need of TESTING! :)
    - World permission implemented (default world permissions for when you are not in a residence zone)​
    - Fixes subzone collision bug.​

    v1.1.2 - BETA
    - Fixed residence admins still requiring IConomy money.​
    - Fixed a bug with TNT explosions.​

    v1.1.1 - BETA
    - Fixed bug breaking subzone permissions.​

    v1.1 - BETA
    - Recusive sub-zoning, make subzones within zones, and then subzones within those subzones :)
    - Different limits based on permissions group​
    - New setting for choosing the selection tool item id.​
    - Anti-lag configuration option.​
    - Moved some permissions into the config file.​
    - All protections are now OFF by default.​

    v1.0.1 - 3/21/2011
    - Added permissions / config option to disable teleports.​

    v1.0 - 3/20/2011
    - Initial Release​

    Bug Reports:
    Please include at minimum the following information with all bug reports:
    • CraftBukkit Version
    • Residence Version
    • What you were doing when the error occurred.
    If available, also include:
    • Any server console error messages
    • Other plugins that may be causing the issue
  2. Offline


    Thank you for your help, will try that :p Yes it's a bit complicated but I'm sure that when you make it work properly, it would be amazing! Tell me, I just hope worldguard doesnt get in conflict with it? What happens if I create a region over a region already created with worldguard? :O
  3. Offline


    Ok so. to respond to the previous permissions comment about it being bad that Residence hooks into Permissions, but doesn't use it for the residence permissions.

    There really isn't any other way to do it. Residence needs to store it's own permissions per residence, otherwise anyone with access to the specific commands will be able to set any residences permissions.

    On Simplifying residence Permission:
    Proposed system - Use something a bit closer to permissions
                subzonedepth: 0-X (0= false)
                - 'buysell'
                - 'create'
                - 'manage.move'
                - 'manage.use'
                - ''
                - 'manage.pvp'
                move: true
                build: true
                use: true
                move: true
                build: false
                tp: false
                admin: false
                use: false
    I think something like this might be a bit easier to manage. current flagaccess should be all associated with a permission tag that is easily defined. in this case, anything with manage.* are user would be able to manage for any residence they create. ownerdefaults are what flags get automatically tagged when the user creates the res, and default are for the non-owner.

    This makes it a bit more intuitive as everything that the user has "permission" to do is rolled into one area, rather than spreading between transaction settings, flagaccess etc.
  4. Offline


    Well, they conflict a little bit... What will happen is you will need permission to build in that area for both worldguard and my plugin. As long as you have permission for both, it should work. Otherwise, the one that you don't have permission for will block you.
  5. Offline


    Allright thank you for the fast answer! Great support :)
  6. Offline


    I like it :) That does make a lot more sense. Especially the subzonedepth thing, I don't know why I made the allow/deny a separate permission when you can just use 0 to disable it. Il try to implement this when I can, I have a lot on my plate right now.
  7. Offline


    I imagine the multi-room necessity for odd-shaped houses is kind of not going away, it's a limitation of using a cuboid based system rather than polygon. And let me tell you... I gave EpicZones a shot, it boasts polygon zoning. I found it unbelievably confusing to use. Trust me, trying to keep track of more than 3-4 "points" of a zone when mapping is a royal pain without any graphic indicators.
  8. Offline


    I'll sign up for the wiki in a few hours, I just need one last tip please ^^

    In my Permissions world config file I have several groups. How do I give them access to the /res commands?
    Although my VIP group is declared in the Residence config file, the VIP members have the "you don't have permission" message whenever they try /res create name.
    They can select areas with the axe though...

    Thank's for the help, and see you soon on the wiki!
  9. Offline


    Right now, you have to give them the "residence.create" permission in your actual permissions config... I've been meaning to move that permission over to my own config file for a while, just havn't done it yet.
    And thanks for the wiki help :)
  10. Offline


    That would be lovely, perhaps make an iConomy price per chunk option as well? Just the "/res select chunk" would be very helpful.

    Thanks for the awesome support, you're exactly what bukkit needs.
  11. Offline


    This Plugin gets greater and greater with every update!!!
    !!!GOOD WORK MAN!!!
    Maybe u can add the feature that u can also set leases on subzones... would be greate.
  12. Offline


    Ok, running 556
    The '/res list' does not display the owner's subzone if he/she doesn't own the zone.
    Setting the enter & leave message to nothing on a zone, then removing both enter & leave (in that order) ends up with enter printing '[zone] null'. An error to look into?
  13. Offline


    Wiki looks good, keep it up.

    Also, I am in favor of a system that lets you auto update your config to the new system (ie copying over old settings and leaving new ones at default).
    And maybe try to release at most of one new version a day or every few days? Fewer releases with more updates is good imo, but I'm not a developer so I couldn't say for sure what is best. I just know it takes me so much time as an admin (on a currently non-public server btw, 3 ppl atm) to keep updating bukkit and plugins I barely have time to play!
    Identity62 likes this.
  14. Offline


    I just found out that if I stop the server, then start it again, the zones don't load. If I remove them, and create them again, they work til I stop it. Which is at least once a day, and I don't like having to redo them all :(
  15. Offline


    Oh yes, Bekvon. I have a small request of you. Could you please take a look at this thread?
    It's from the developer of McMMO. Apparently the block protection used in mods like WorldGuard, Towny (and assumedly this mod Residence), have issues with the way some of the skills in his mod allow you to instantly break certain blocks. He posts a simple solution for full compatibility. Just wondering if you could have a glance and make the required change (if its not already compatible). Thanks!
  16. Offline


    Mmm, you mean a diffent price for if you buy the whole chunk? kinda like a discount for buying in bulk lol? Yea, could probbably do that :)

    Thanks :)
    And yup, going to add that ability in.

    Hmm, ok the non-listing subzone thing I can fix, I didn't take that into account...
    Not quite sure I know what you mean on the second thing. First you set it to nothing, then you removed it? isnt that the same thing? Wait, you mean if you use the remove command on it twice it give that message? Interesting.... :oops:

    Yea, I will be releasing slower now, and il try to make a converter for old format to new.

    Hmm, your using latest Residence version with CB 556? Try this, open up your config file and find the setting called "saveFormat: dat", and change it to "saveFormat: yml" and see if it works. Some people were having trouble with the .dat format, so I made a .yml save format. This will also allow you to modify residences offline since .yml is the same easy format as config files.

    Yup, I posted what I hope is a potential fix for him for all protection mods, will see if it works :)
  17. Offline


    This is by far the best protection you can get. I wish when you created a zone it would auto block building rights
  18. Offline


    I have only one issue with this plugin, when you deny the 'move' flag for a certain group or player and they enter it, they ALWAYS move to the southwest!
    Can you make it so that you can adjust where the players get spawned once they enter a region they are not supposed to be in?
    Or even better can you make people not even teleport and just not let them in a region that has 'move' set to false.
  19. Offline


    This is a fantastic plugin, but I was just wondering if there was a way to delete subzones? I've looked through all of the commands but nothing works? If there isn't a way, could you please consider adding it? Thanks.
  20. Offline


    You can do that by setting "build: false" under default flags in the config... And sorry, I know the config is confusing, I will be making a new config layout when I can :)

    I origionally was simply teleporting people back to their previous position when they tried to enter an area, however, I found that if they kept holding the forward button they would slowly keep moving into the zone. The reason is that, teleporting people often does not put them back quite where they came from, its a tiny bit random. Hopefully once the bukkit people offer a working way to simply cancel movement rather then making us teleport them back to whence they came, it will be a viable possibility :)

    Yea, use "/res remove parentzone.subzone"
    Also, see my "Usage Notes" section in the OP, as I actually have an example under it.
  21. Offline


    My goal is to make this as simple as possible for people on my server. They buy a chunk at a time, it's automatically protected (which I can do thanks to your lovely default flags), and then they can adjust other flags if they want to. Hopefully there's no more complaining after this, haha. :)
  22. Offline


    When a player creates a residence he can name it. Is it possible that the residence takes his name only?

    Also, how to remove a residence?
  23. Offline

    Steve Cole

    I also get this error about every 10 seconds and when i got home today the console was being spammed with "[SEVERE] Could not pass event BLOCK_IGNITE to Residence" about 10 times every second.

    didn't want to paste my server log here so i uploaded a copy to my site if you want to read it.
    server log
    the original log was 116mb but i removed the majority of the repeated error messages which brought the size down to 17kb just to give you an idea of how many error messages there were. also the server had only been running a day or two. with only a few hours of people actually playing on it.

    the server is running Craftbukkit version git-Bukkit-0.0.0-544-g6c6c30a-b556jnks
  24. Offline


    It has been in .yml format since before you made it the default option. The residences all look right in the file too.
  25. Offline


    I have another request of you Bekvon :))

    This mod was resulting in tons of errors/conflicts with Essentials.Protection so I disabled Essentials.Protection.. Residence is far superior atm imho. What I would like however are a few simple additions.

    1. Ability to make global (world-wide) flags
    2. Ability to blacklist individual blocks within zones/subzones
    Essentials.Protect is a very basic protection plugin, but it has some small features that I think would work wonderfully with Residence. To give you an idea (if you don't already know) I am posting the snipper of code from the config.yml Essentials uses that show what it does. Hopefully you can work with it :)

      # Database settings for sign/rail protection
      # get mysql.jar and sqlite and place it in your serverroot/lib directory from here:
      # mysql, sqlite or none
      datatype: 'sqlite'
      # If you specified MySQL above, you MUST enter the appropriate details here.
      # If you specified SQLite above, these will be IGNORED.
      username: 'root'
      password: 'root'
      mysqlDb: 'jdbc:mysql://localhost:3306/minecraft'
      # For which block types would you like to be alerted?
      # You can find a list of IDs in plugins/Essentials/Items.db after loading Essentials for the first time.
        # 10: lava
        # 11: still lava
        # 46: TNT
        on-placement: 10,11,46
        # 1: rock (just an example--doesn't actually do much)
        on-use: 1
        # 46: TNT
        on-break: 46
      # Users cannot PLACE these types of blocks/items.
      # < 255 designates a BLOCK
      # > 255 designates an ITEM (Some blocks can be placed as blocks OR items; lava blocks can be placed by lava buckets, for example.)
        placement: 327,326,14,56,46,11,10,9,8
        usage: 327,326,325
      # General physics/behavior modifications
        lava-flow: false
        water-flow: false
        water-bucket-flow: false
        fire-spread: true
        lava-fire-spread: true
        flint-fire: false
        tnt-explosion: false
        creeper-explosion: true
        creeper-playerdamage: true
        creeper-blockdamage: true
        # Prevent the spawning of creatures
          creeper: false
          ghast: false
          slime: true
      # Maximum height the creeper should explode. -1 allows them to explode everywhere.
      # Set prevent.creeper-explosion to true, if you want to disable creeper explosions.
        max-height: -1
      # Protect various blocks.
        # Protect all signs
        signs: true
        # Prevent users from destroying rails
        rails: true
        # Blocks below rails/signs are also protected if the respective rail/sign is protected.
        # This makes it more difficult to circumvent protection, and should be enabled.
        # This only has an effect if "rails" or "signs" is also enabled.
        block-below: true
       # Prevent placing blocks above protected rails, this is to stop a potential griefing
        prevent-block-on-rails: false
      # Disable various default physics and behaviors
        # Should fall damage be disabled?
        fall: false
        # Users with the essentials.protect.pvp permission will still be able to attack each other if this is set to true.
        # They will be unable to attack users without that same permission node.
        pvp: false
        # Should drowning damage be disabled?
        # (Split into two behaviors; generally, you want both set to the same value)
        drown: false
        suffocate: false
        # Should damage via lava be disabled?  Items that fall into lava will still burn to a crisp. ;)
        lavadmg: false
        # Should arrows cause damage?
        projectiles: false
        # This will disable damage from touching cacti.
        contactdmg: false
        # Burn, baby, burn!  Should fire damage be disabled?
        firedmg: false
        # Should people with build: false in permissions be allowed to build
        # Set true to disable building for those people
        build: false
    Thanks bud!
  26. Offline


    To delete a subzone, use /res remove parentzone.subzone
    For example, I have the subzone Basement in the zone House. That would mean:
    /res remove House.Basement
  27. Offline

    Nat Ryall

    Try updating to 1.2.5, I haven't had it since.
  28. Offline


    Alright since I wrote out a bit of a way to simplify permissions I think the COmmand system can be simplified:

    And here's my suggestion
    OLD: /res set <residence> <flag> <t/f>
    NEW: /res <residence> +/-<flag>

    When modifying flags on a residence I feel 'set' shouldn't be needed.
    for example to set monsters off or on while standing inside the residence it would be as simple as:
    /res -monsters
    /res +monsters

    to set player or group flags you would:
    /res gset <group> +use
    /res pset <player> -move


    using 'flag true/false' is longhand way that seems like it could be simplified to a +/- system. especially since this is how they are expressed in the printout.
  29. Offline

    Steve Cole

    Thanks, it worked for me too.

    I would also like the ability to stop the placement, destruction, or ignition of certain blocks globally and per residence.

    it might be asking alot and I know it would take time to implement but the Sign protection database thing would also be a nice feature to add.

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


    Essentials.Protect has never worked properly for me. It'd be better to just use LWC imo.

    Also: for some reason Residence keeps corrupting my save files. Maybe I should clean it out and start fresh? But It does make me wonder if Residence is writing bad data. (Why does it need to save every x minutes when leasing is disabled anyway?)

    Just realised I was using 1.2.2, was this fixed in current revision?

    Any chance of this getting open-sourced? so we can help with things or develop features?
  31. Offline


    Can we PLEASE get this updated to Craftbukkit build 602? That would be great :D
Thread Status:
Not open for further replies.

Share This Page