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

    Daniel Few

    :p it's now in the wiki anyway, look under 'Tag Explanation' in 'Creating, Modifying and Protecting a Residence'

    EVERYONE: as i've said before please say if there is anything you do not understand, or a part of the wiki that isn't clear so i can update it :)
  3. Offline


    No worries.

    Nice work on the wiki, it's coming on good :). I'll just assume that the ItemList thingie I asked about earlier is not finished as I can't see any updates on that (and all my tests have pretty much confirmed that that's the case anyway).

    @bekvon: I have a friend of mine that is a very competent Java coder and was looking for a project to play around with. I pointed him to this direction if you don't mind. He'll only be playing around with it for starters but I'll let you know if he adds anything useful that you might be able to use. It's the least I can do.
  4. Offline

    Daniel Few

    Heya, Firstly, thanks :) ItemList is new to me :p i've been away for five days, and i think it was added then so i'll have to check that out, but i'll add it to the wiki as soon as i can :)
  5. Offline


    Is there any way we can set a min z-axis height an area can be placed?.. I want to allow people to buy residences freely but I don't want them making their mines protected... I don't think they should feel safe when they find a cave and spend a little money to protect it.
  6. Offline


    Hey all :) Just uploaded a new snapshot build that allows World flags (flags for when your outside a residence) to be set per world, and per group. Config file has changed a little to accommodate these settings, grab the newest config snapshot :) Also, item blacklisting / whitelisting is ready to be tested, its the last section of the config. You can make as many blacklists / whitelists as you want and apply them to specific groups / specific worlds, or you can simply make a all encompassing list that applys to everyone. :) Also I added a "info tool" which by default is String. You can simply equip the info tool and click in a residence with it and it will show you the info for the residence.

    That's a good idea, I can add probably add a feature to do that :)
  7. Offline

    Daniel Few

  8. Offline


    You can't switch to TNT if it's blacklisted. But you still can put it in your "empty hand" from the inventory and use it after.

    And is there some way to use things like /resadmin setowner without typing the whole residence name over and over? Like /res set works if you sand inside the residence you want to change. It should be made possible for all commands that use a residence name.

    edit: /res select residence doesnt work.

    edit2: will it ever be possible to just extend a existing residence with commands like /res expand N ? Or will that be possible with /res select expand?
  9. Offline


    Yay! New version!

    First off: So, the whitelist/blacklist doesn't work as I thought it would. I thought it would be directly related to residences, so you're basically blacklisting certain items to be used/placed on that residence, which seemed logical to me. Instead it looks like a separate feature from everything related to residences, it blocks the user from even selecting the item in the toolbar. I have to say I don't like the feature at all :(. My hope for this feature was to have the Itemlists directly related to the use: and build: flags so that, for example, if a residence has build: false but a whitelist with 'TORCH' on it, people would still be able to place torches in it.

    Bug: I tried a whitelist with the following settings believing it would allow people to destroy LOG and LEAVES no matter what build protection residences had:
            Type: whitelist
            World: world
               - 'LOG'
               - 'LEAVES'
    Obviously it didn't work as I intended it to, but also as I scrolled around my toolbar (now containing only blacklisted items) the game lagged horribly until it finally froze and crashed. The server didn't output any error as it would seem the problem was client-side, but obviously related to the force-switching of items in the toolbar and no available whitelisted item to choose from. This might be a rare bug unless you have a lot of blacklisted items, but still thought it worth mentioning.

    This is a great update none-the-less and I can't stop mentioning how grateful I am for your work!

    If you believe the ToDo list (- Add some command aliases.), it seems more aliases are on the way :). In the meantime I suggest trying out CommandHelper which allows you to make any custom command aliases. It's very powerful, albeit a bit complicated to use.

    Edit: Extending can currently be done by adding areas to a residence after making a new selection. Although I agree it would be nice to have a quick way of just "adding x blocks on the y side of a residence".

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


    Ok, I'll see if I can fix the blacklist thing. I'm probably just going to have to move the check to when you use the item, rather then just blocking you from equipping it.

    Il see whats wrong with /res select residence, I cant remember if i tested it.

    You mean to extend a already existing residence? Hmm, yea something like that can be done :)

    Hmm, yea these item blacklist / whitelists are basically just to provide a way to prevent users from using certain items at all. Making whitelists / blacklists ignored in residences wouldn't be too hard though, I could add a simple true/false value to the list for making it do that. Maybe instead I'll make a new list type, a "ignorelist" that will basically cause certain blocks to ignore residences settings? Some ideas.
    I will eventually get around to adding aliases hehe :) I would like to make all the command configurable eventually, but that's on low priority at the moment.
  11. Offline


    Would it be possible to show which residence one is colliding with when you try to create a new one?

    I've spent so much time trying to figure out which res I'm colliding with it's mind numbing, heh.

    Also is there a way to disable (from a command) enter/leave messages individually? So if a player wants an enter message but not a leave one, they can not have to set the leave message to something just so it's set.
  12. Offline


    Can you update with build 714 ? Because actually, flag dont works :(
  13. Offline


    I'm struggling to understand something here and was hoping for a bit of advice.

    /res area is the command for adding areas to a residence? So if I create EXAMPLE1 residence, I can then use my wooden axe to select another area, and that area can be appended to EXAMPLE1 residence?

    My problem comes from needing to make far too many residences. My territory is against a number of other people's territories. I need to select lots of oddly shaped areas but making hundreds of residences is a permissions management nightmare.

    So here is what I did to try and make this work:

    1. Select primary/secondary cordinates. Type in /res select vert.
    2. Type in /res create EXAMPLE1 (Successful)
    3. Move out of the residence, and repeate step 1.
    4. type in /res area add EXAMPLE1 main

    I get the error message: "An internet error occurred while attempting this command"

    Now, I'm unfamiliar with the term "areas". I'm assuming an "area" is a selection of space that has not yet been made into a residence?

    I also notice that every residence I have by default is tagged as being "Current Area ID: Main"

    Is that how it's supposed to be?

    Any how, I paged through the Wiki on /res and spoke to a skilled plugin admin on my server and even he cannot figure things out.

    As I said earlier, I'm simply looking to append selections of land to my already created residences. I would be most grateful for any help on this. Thank you!
  14. Offline


    My issue is fixed. I'm just retarded, apparently :/
  15. Offline


    Yup, that shouldn't be to hard to do :) And as for the leave messages, you can remove them either by deleting the leave message line in the config file, or with this command: "/res message <residence> remove leave"
    Hmm, I've been using build 699 as my testing grounds, I should probbably update. Do you get any console errors under 714?

    Don't worry, you actually have figured it all out :) Areas are exactly what your looking for, as they let you add more land to a existing residence. Looks like theres a bug in area creation though, whenever you get the internal error message, can you see if it outputs a error on the server console? Paste that error here so I can see it :)

    Lol, well glad you got it working :)
  16. Offline


    Saweet! I wondered if there wasn't a command for it, but my help-fu skills didn't find it.

    Great plugin by the way. A bit of a learning curve, but after you initially train a few users on how to use it, they train others and eventually admins/ops can just let their user base answer their own questions on it.
  17. Offline


    How can i disable the /res TP command for everyone? I tried:
            Global: #these are default for all worlds unless specified below, they can be overridden per group
                use: true
                build: true
                ignite: true
                firespread: true
                damage: true
                creeper: true
                tnt: true
                pvp: true
                tp: false

              #these flags will override the flags at the top, under the Global section.
                    Global: #these flags will apply to all worlds
                         tp: false

    but people can still TP :(
  18. Offline


    I had a question with the OP controls. OPs are allowed by default to exceed size limitations. This is ok but was wondering if you could set up an option to turn this on/off in config, and also if this is on that any res they make over the size limitation would be "Server" land and used for markets/etc and had a seperate set of flags. Don't know if this is possible or worth your time, but would be great for me if it would be. Thank you greatly for your time in working on this plugin.
  19. Offline


    I got a little idea,.... would be possible to somehow bind tamed wolf to residence,... so he would guard it,..?
    Like when somebody trespass your residence, and get close to your tamed wolf he will become agressive and attack the trespasser till he die or get our your residence....?
  20. Offline


    I'm one of the admins from the server Dave is one. what we're seeing on the console is a NullPointerException on line 169 of, the main admin hasn't updated the plugin for a little while, we're waiting on things to get updated for 1.5 right now.

    I don't know which build of 2.0 we're using, but we've got an md5sum of 6ccdc2568e683d84b817892f0473fdfb for the jar. If you need to i can go through all the compiled sets you've had on github and find the date for you.
  21. Offline


    One more question from me: If a residence has, say -pvp, and the subzone doesn't have any flag, shouldn't then the main zone's flags inherit to the subzones, so if i dont set the pvp flag in the subzone, it takes the flag from the parent zone? I think that was the case in the 1.x+ version but doesn't work in 2.0 anymore
  22. Offline


    @bekvon Whats about the progress of the Residence-Converter?
  23. Offline


    Nothing in console but, the flag build don't works, all of my players can't build :/
  24. Offline


    I've been able to build just fine on 714.
  25. Offline

    Daniel Few

    If this was going to be implemented, it might be a good idea to have a command that sets the current selection to 'server land'. This way it can just be turned on or off and wouldn't depend on it being over a certain size. Eg when you've set your area, type '/res create <residence name> [server]' - server is optional and would set it to server land.
  26. Offline


    Is it possible to allow the residence owner to set a lease amount for a subzone instead of having admins only able to set it?
  27. Offline


    Hum okay i'let's retry
  28. Offline


    ok i need to know if this is just me or not, i have setup residence with permissions and for some reason my normal members are able to use/res, and /res delete but they can use /res create how can this be?
  29. Offline


    Can't buy or sell land, says iConomy account is not found. Any clue as to what to do?
  30. Offline


    Hey all, I am away from home for a couple days again, and so I will only be on the forums intermittently. I am still thinking about how to best implement the rent system, as well as your other feature requests. I'll also still be working on Residence while I'm away, as I have my laptop and brought the code with me :) I also am looking to go ahead and get 2.0 out of the Alpha stages pretty soon, so expect work on a v1.X to 2.0 save converter soon. I'd also like to thank the people who've donated, it is greatly appreciated! :D

    tp is a flag that residence owners can set to give people permission to teleport to their residence, it is not the control for the actual tp command. To deny tp access to a certain group, look for the CanTeleport true/false setting under each group in the config file. :) You can either delete the line, or set it to false, either one should disable teleport for that group.
    Yea, I guess I should add some sort of OP = admin config option so you can enable / disable that specifically. I will add it to the todo :) Server owned land is on the way too.
    That's a really cool idea! Although it would make a better Residence addon (separate plugin). Also I'm no good at AI programming heh :oops: Most of the core residence functions are available to other plugins though, so its entirely possible for someone to create one :)
    Ok, I'll try to take a look at whats going on. It may be something that has been fixed already, but maybe not. If you could find the GitHub commit for me that would be great, but I'll probably just look through the code and try to find any errors. :)
    There was never any permission inheritance in Residence, however if memory serves correctly, I believe that subzones automatically copied their parents permissions on creation, back in v1.0. I suppose I could bring that little feature back, although it can be done manually right now with the /res mirror command. Also, it actually would be pretty easy to implement inheritable permission in the current code base, I'm just not sure if everyone would want that, since some people want to create a big zone and then sell the subzones as separate residences. Perhaps another config option to enable inheritance could work? :)
    Not much progress on that, but I think I will be getting to it very soon because I do want to goahead and get 2.0 out of Alpha status. :)
    Ahh, that's a good idea :) Shouldn't be to hard to do either.
    The owner can renew his own lease. The amount of time each renew gives the player is in the config file under each group's lease settings. The player cannot just strait up set his own lease time, as that defeats the real purpose of the system :)
    Are you using 1.X or 2.0? In version 1.X, you need to give them the "residence.create" permission, however in 2.0 it has been moved to the config file, under each group there is a CanCreate option.
    Are you using version 1.X? there is a bug in the v1.X releases related to iConomy. iConomy's account names are case sensitive and Residence was storing player names in their lowercase format. This causes anyone with uppercase letters in their name to not be able to buy or sell. This has been fixed in v2.0, as player names are now stored case sensitively.
  31. Offline



    Fantastic plugin, am testing 2.0 as good as possible, and so far it works as I want.

    *Except* one thing: I simply cannot use the defined tool to select a residence! No matter if I use the default item, set any other item, whatever, I cannot select points, left and rightclicks dont give any feedback. The only way for me to create residences is using the /res select x y z.

    Am I missing something really stupid? Because everything else works perfect.


    One little more thing: Is it possible to set the max amount of residences on a per-world-basis? E.g., I want a certain group to be able to claim 2 residences on world X and only one residence on world Y. This would be fabulous!
Thread Status:
Not open for further replies.

Share This Page