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


    17:18:01 [INFO] [Residence] Found Permissions Plugin!
    17:18:01 [SEVERE] com/nijiko/coelho/iConomy/iConomy loading Residence vv1.2.8
    TA (Is it up to date?)
    java.lang.NoClassDefFoundError: com/nijiko/coelho/iConomy/iConomy
            at com.bekvon.bukkit.residence.Residence.checkIConomy(
            at com.bekvon.bukkit.residence.Residence.onEnable(
            at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginMan
            at org.bukkit.craftbukkit.CraftServer.loadPlugin(
            at org.bukkit.craftbukkit.CraftServer.loadPlugins(
            at net.minecraft.server.MinecraftServer.e(
            at net.minecraft.server.MinecraftServer.a(
            at net.minecraft.server.MinecraftServer.d(
    Caused by: java.lang.ClassNotFoundException: com.nijiko.coelho.iConomy.iConom
            at$ Source)
            at Method)
            at Source)
            at java.lang.ClassLoader.loadClass(Unknown Source)
            at java.lang.ClassLoader.loadClass(Unknown Source)
            ... 12 more
    I keep getting the above error, and I have no idea what's causing it. I'm running bukkit 677 right now ( just downgraded from 684 to see if it was just a update issue.) Any idea what's causing it?
  3. Offline

    Daniel Few

    I think using residence 2.0 would fix that.
  4. Offline


    very nice plugin however i was wondering if u could make it autosave everytime a new residence is made =|?
    other then that, i would like to request that the ability to delete residences should have a seperate node.... i simply find everyone being able to stand on the main zone and delete it worrying
    a permission node to ignore stuff without giving residence.admin would be very nice too
  5. Offline


    Yup :D

    Is it another permissions thing? or is it not letting you even as admin? Subzones have to be contained within their parent zone, so both selection points need to be inside it. What specific message are you getting?
    Yea, use "/res pset <residence> <player> <flag> <true/false>"

    I guess I could make some more advanced save options including a save on creation option. Not to high on my todo list though. Also, the only person who can remove a residence is the owner or a OP/Admin. If someone else owns a subzone, they can only remove that subzone, not the main zone. Even if you set the "admin" flag to true for someone on the residence, they can't remove it. So, it shouldn't be possible for anyone to stand on the main zone and delete it. Perhaps I should make the remove command require you to type the full name of the residence, rather then just allowing you to stand in it.
  6. Offline



    How do I expand 10 up and 10 down, essentially with commands, ie WG - //expand 10 10 u

    I'll try it out again.

    Also I notice you have residence save, why not just integrate a whole world save, i.e. "Auto-Save" It's what I use now.. It's timed server saves with intervals in (s)... and it only queue's if there is an active user entity on the server, I think the same should be done if you decide to not do my suggestion.. about the ONLY SAVES IF USERS ARE ON! :)

    P.S. EP13 Was awesome :D
  7. Offline


    Hmm I did. Well that was before I messed up and apparently hit the wrong link.

    OHHHH I know what did it. When I was editing the config I had just gotten notepad++ and it didn't have tabs set to spaces yet... That might have been the cause of the original error. My bad, sorry for wasting your time. :p Should work now (testing now :p )
  8. Offline


    Can you make this mcMMO Compatible? It still levels you if you have no permission or in pvp zone.

    And you can take damage based on the skills :p
  9. Offline


    Running this plugin on build #705 with no errors! 1.5 compatible =D
  10. Offline


    You mean save residences whenever the world saves? I had thought of that, and for some reason I decided not too, and now I cant remember why...:oops: As for only saving when users are on, yea I can do that :)
    P.S. Yes it was :D

    Mmm, I think I can do something about that, it would involve simply doing residence checks before other plugins do their checks. The only problem with this, is that its possible a plugin could un-cancel a event that residence prevents, but I don't know of any plugins that un-cancel events, so its probably safe :)

    Awesome :D glad to hear!
  11. Offline


    Again, thanks @bekvon for a wonderful plugin, can't be without it!

    At the moment I find that a user with CanCreate: false, still have access to way too many commands and even the selection wand. I know they don't really have much effect but it helps keeping the available commands to a minimum for those who don't need them. The wand item also clutters the chat down with confusing and unnecessary information if someone who can't create residences uses it.

    I suggest making all commands related to creating a residence (e.g. /res select, /res remove, /res subzone) competely unavailable (just like /res create is ) when CanCreate is false for a group. I also suggest hiding the wand messages if that is the case.

    Also, why was the permission node residence.create moved to the CanCreate in config? I prefer it many times over to have all the permissions settings in one file, Permissions node are brilliant and allows admins a lot of power and customisation. I would suggest, not only bringing it back but also adding more nodes, like residence.use, that allows/disallows users to even use the residence system (buy residences for example), as at the moment, even Guests on my server would be able to buy a residence. EDIT: Completely forgot about the CanBuy setting. But I STILL think Permission nodes are a good idea :).
  12. Offline


    Nvm after all...
  13. Offline


    For me, people can't buy/sell residences. CanBuy is true, it's not with the config, i believe.

    #These are Global Settings for Residence.
        # Wooden Axe is the default selection tool for Residence.
        # You can change it to another item ID listed here:
        SelectionToolId: 271
        # The interval, in milliseconds, between movement checks.
       # Reducing this will increase the load on the server.
       # Increasing this will allow players to move further in movement restricted zones before they are teleported out.
        MoveCheckInterval: 500
        # The interval, in minutes, between residence saves.
        SaveInterval: 10
        # The default group to use if Permissions fails to attach or your not using Permissions.
        DefaultGroup: default
        # Enable / Disable the Lease System.
        UseLeaseSystem: false
        # The interval, in minutes, between residence lease checks (if leases are enabled).
        LeaseCheckInterval: 100000000000000000000
        # Whether or not to use the Permissions system in conjunction with this config.
        EnablePermissions: true
        # Enable / Disable Residence's Economy System.
        EnableEconomy: false
        # The economy system to use (iConomy or MineConomy).
        EconomySystem: iConomy
        # Whether or not to ignore the usual Permission flags and only allow OPs and groups with 'residence.admin' to change residences.
        AdminOnlyCommands: false
        # These flags are applied, by default, when the player is not within another residence.
        # All flags default to true if not specified.
            use: true
            build: true
            ignite: true
            firespread: true
            damage: true
            creeper: true
            tnt: true
            pvp: true
    # These groups correspond to the Permissions groups defined in your '<worldname>.yml'
           # Information about the Residence zone that the player can define.
               # Determins if this group can create residences or not.
               CanCreate: true
               # The maximum number of Residences a player can have.
               MaxResidences: 3
               # The maximum number of physical areas a residence can have.
               MaxAreasPerResidence: 2
               # The maximum number of blocks a Residence can be, East to West (X).
               MaxEastWest: 16
               # The maximum number of blocks a Residence can be, North to South (Z).
               MaxNorthSouth: 16
               # The maximum number of blocks a Residence can be, High to Low (Y).
               MaxUpDown: 256
                # The maximum recursive depth that subzones can go.
                # A subzone within a subzone within the Residence zone would be a depth of 2.
                # Set to 0 to disable subzones.
               SubzoneDepth: 3
               # Whether or not to allow teleporting to Residences.
               CanTeleport: true
           # Options relating to enter and leave messages on the residence.
               # Whether or not the player can change the Residence enter and/or leave message.
               CanChange: true
               # The default enter message to apply to new Residences created by players in this group.
               # Leaving the message blank will disable it.
               DefaultEnter: Welcome %player to %residence, owned by %owner.
               # The default leave message to apply to new Residences created by players in this group.
               # Leaving the message blank will disable it.
               DefaultLeave: Now leaving %residence.
           # Options relating to the leasing of zones.
              # The maximum number of days to allow leases.
              MaxDays: 16
              # The number of days to add to the lease following a '/res lease renew' command.
              RenewIncrement: 14
           # Options relating to the Residence Economy.
              # Whether or not players in this group can buy other Residences that are for sale.
              CanBuy: true
              # Whether or not players in this group can sell their Residences.
              CanSell: true
              # Whether or not to ignore the Residence size/count limits when buying a residence.
              IgnoreLimits: false
              # The cost, per block, of buying a Residence or adding a area to it.
              BuyCost: 0.05
              # The cost, per block, of renewing a Residence lease.
              RenewCost: 0.02
           # Flags are checked in the order:
           # 1: Player (in-game only)
           # 2: Group
           # 3: Owner
           # 4: Default
           # 5: Otherwise, if all others are undefined, defaults to 'true'.
           # Flag permissions default to false.
              # Specifys the flags that players of this group are allowed to change.
                   move: true
                   build: true
                   use: true
              # Specifys the flags that are applied at residence creation for players of this group.
                   build: false
                   use: false
                   tnt: false
                   creeper: false
                   firespread: false
                   container: false
              # Specifys the flags that are applied at to the creator at residence creation.
                   move: true
                   build: true
                   use: true
                   container: true
              # Specifys the flags that are applied to other groups for this residence, at creation.
                       #move: true
    # You can manually specify the group a player is in below, this overrides their permissions group.
         bekvon: default
         player: default
            Type: blacklist
            World: world
            Group: default
    By the way, owners can't change leave/enter messages, it says, that it's disabled. The enter/leave messages are nothing, if not changed manually. I feel like it doesn't read parts of the config. CB 677. If you need any info, ask me. By the way, OMFGASUM plugin!!1one2!
  14. I apologise if I've missed something, but i have two questions/suggestions (if you cant do what i'm asking can it be made possible).

    Firstly, is it possible to give different groups different flags for the world at large.:

    There is a section in the config:
    # These flags are applied, by default, when the player is not within another residence. # All flags default to true if not specified.

    But it doesn't say if I could override those flags for certain groups... such as make it so the 'newbie' group could have build:false.

    Secondly, is it possible to give someone access to be able to create/modify subzones without being able to modify the larger zone.

    Ie they would have the 'create' flag on the parent zone, and any subzone they create they would get 'admin'.
  15. Offline


    After reading your post, I tried it also... works fine for me as well in #705. I also found Residence v2.0 works along with #705 and Essentials 2.1 without updating. Sweet!!

    - 65Wolf
  16. Offline


    Also, allowing pvp in a certain zone doesn't seem to work.
  17. Offline


    Good idea on the selection commands, however they aren't completely useless when you have CanCreate set to false, because you can still make subzones using them. So basically, what I could do is add a check to see if both CanCreate is false AND the MaxSubzoneDepth setting is zero, then disable the selection tools. Sound good?

    Also for permissions nodes, the reason it was moved to the config file was so that people who weren't using permissions could still have some control over the plugin. Honestly, it works almost the exact same way as a permission node, because if you want to you can just remove it from the config and it should treat it as false. And actually, config options are more powerful then permission nodes, because permission nodes cant have a value. I.E. you can't have the permission node "Default.EnterMessage = hi this is a message" This is why all I do from permissions is pull a users group, and then keep all the actual settings under my own config, its actually more powerful this way :) The only thing you lose is group inheritance, which I may actually fix one day when I get time, as it shouldn't be too hard. :) I suppose that the ideal solution would be to use a combination of permissions and a config file, but like I said, I wanted to provide options for people not using Permissions.

    I see your problem, its cause you set the LeaseCheckInterval to some incredibly high number lol. :D LeaseCheckInterval is a Java Integer, which has a range of between roughly 2 billion and negative 2 billion, so it blew in the config file at that point. Set it to like 9999999, or something a little smaller heh.

    At the moment, no you cant give different permissions to the world for users, but that will change. I will probably be moving world flags under the Groups section so that you can set it for each Group. Alternatively, I may keep it its own section, and instead allow you to both set default flags both by Group and by individual World, which would be more powerful :)

    And I will think about adding a subzone flag so that you can grant others the ability to make subzones. At the moment, you can make a subzone for them and then sell it to them. I also plan to make a command where you can just give a zone or subzone you own to somone else. :) A admin can also transfer ownership of it for you right now.

    You need to set the server's pvp flag to true under the file for any pvp to work, try that and see if it works :)
  18. Thanks bekvon. My plan is to prevent the 'newbie' group from building in any areas except from areas which have been designated as 'newbie build zones'. The server staff will set up a couple of these areas so that they can play before they gain public build rights. This is the feature I'm really looking forward too.

    The second part would be useful because it would allow the staff to set up specific zones on the server like a pvp free zone around a city, whilst still allow people to create residences themselves inside.
  19. Offline


    Sounds perfect. My mind slipped again forgetting about the subzones setting.
    I didn't mean that Permissions should completely replace a config, far from it, I just think that it's handy to have both, and control everything group/permission related with Permissions, but I see your point with compatibility.

    Thanks for replying so quickly and actually reading through my walls of text :). I'll try to get my PayPal account up and running again (damn security features..) so I can give a little support for your brilliant work.
  20. Offline


    is there a way to check residence info without typing info? Like region does with string? That'd be a handy tool! also, changing wooden axe to wooden hoe does not change the txt in help chat.
  21. Offline


    COMMENCE MASSIVE FACEPALM. I set the lease check to uber high, because i don't want to use that system, and i thought, that setting it this high will be 1 check less per residence. Actually idk why i did it :D Thanks!

    About the pvp - yea, i did set it in the I had to restart a few times to get it to work, but SUDDENLY it worked.

    TYSM! An awesome plugin :)
  22. Offline


    I'm back. Have you got any hints on how the last few lines in the config work, i.e. the ItemList: ?

    After trying many different settings and options I'm starting to think that's a feature not yet implemented.
  23. Offline


    will be good if in "/res set ?" will appear only the flags the player can change.
  24. Offline


    BAD NEWS. STILL NOT WORKING. I still can't buy/sell residences. I changed the uber-huge config value to 10, but still it doesn't work. CanBuy and CanSell are true
  25. Offline

    Daniel Few

    Heya, i'm gunna carry on with the config wiki page now so look back in an hour or two for updates. I'll see how much i can get done :)
    Nelien likes this.
  26. Offline


    So, what about saving residences during onDisable event? :)
  27. Offline


    Can you clear up specifically what true/false actually corresponds to in the flags: specifically flow explosion fire damage and monster. the {wiki} does not even seam to know whether true protects residence from this or allows this to happen.
  28. Offline


    As bekvon sais above, the wiki is far from finished. This is what I learned: true means that what the flag describes is allowed, e.g. firespread = true means firespread is allowed, i.e. fire will spread. The opposite is true for a flag set to false, e.g. use = false means the specified group will not be able to use items in this residence.
    Felonu likes this.
  29. Offline


    thanks Nelien that's what I had found too and thought, but it's good to see confirmation from someone else... did not want to test too much with lava etc.
  30. Offline

    Daniel Few

    Sorry, i'll put that in.

    TRUE always means it CAN happen. Eg. Fire = fires CAN be started. Build = People CAN build. I'll add this into the wiki now.

    EDIT: oops sorry Nielien, didn't see your post there. Much better description then this :)

    Here is a small explanation of what TRUE and FALSE means. It;s in the wiki on this page:, protecting and modifying a seclection

    I'm gunna carry on with the configuration section now.

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


    Thank you for your clarification too daniel.

    This makes it clear in not uncertain terms.
Thread Status:
Not open for further replies.

Share This Page