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


    I have a problem with my flags. NONE of them are working. My spawn city keeps going on fire. Even though firespread is set to false and ignite is set to false. And monsters keep spawning. Any help? I really need this to work, cous i am migrating my server from iZone.
  3. Offline


    Could someone talk me through how to add more land to an existing residence without editing the res.yml file? I know the command is /res area add [residence] [areaid] but where do i get this area id and can i not just mark out an area with my selection tool and add it to the residence?
  4. Offline


    ok, select your area you want to add (it can overlap) then do: /res area add [residence] [name to call the new area]
    areaid is not a previously created area but what you want to ID the one your creating. (so then you can do /res area remove [res] [areaID] to kill the extension if you wish.)

    im guessing the spawn area is protected. so the best idea would be to post your config (pastebin or attachment please) so people can see what's going wrong. also if you do a '/res info' call within the residence, whats the flags set on the property (if any?)
  5. Offline


    On my server we are making a city and we are using this plugin to protect the different house areas.
    But I want to protect the streets and the walls as well. What is the most optimal way of protecting the whole city but still allowing players to build on their areas....
    I tried Residence + EpicZones. But epiczone overlaps the Residence build permissions so no one can build on their areas :(

    Please help me
    Thank you in advance
  6. Offline


    i have a main area (town with streets) and i then subzone areas within the main area which i sell to the players, so the streets are yours, and the subzone is theirs to do whatever with. (the properties will just be named town.01, etc)
  7. Offline


    Oh fucking awesome. Didn't know you could sell subzones as with residences

    Thank you very much!
  8. Offline


  9. Offline


    I type /resadmin setowner city.jailhouse Player
    It doesn't work says invalid residence
    EDIT: it works, The beginning of the letter J looked like a dot so I misspelled the name xD
  10. Offline


    The server is full all the time. So it might take some time. I will make a screenshot of the info thing and a pastebin of the config.
  11. Offline


    couple of Qs

    first i define the X,Y,Z of my main city then i do /res create maincity

    then when i create subzone eg /res subzone maincity themine

    but how do i add flags for the subzone ? so only certain ppl can build/move ?

    thanks in advance
  12. Offline


    Could someone please advice me on this? Would updating CB fix this?
  13. Offline


    all good, just happy it works like i said it would XD
    the flags for the subzone work the same as a main residence. stand in it and do the /res set/pset/gset commands like normal. (or access the property using maincity.themine as the name)
    also the property should get the default flags which you define for each group within the config.yml
    the size issue can be fixed setting the height setting to 128 and the max/min values to 127 and 0. (i believe that was the fix)
    and for issue 2, have you tried setting the player as the owner? /resadmin setowner RES_NAME PLAYER_NAME
  14. Offline


    thanks for that e_zach will give it a try i was confused whne looking at the commands as it says wjen setting up a flag to type /res set <resname> flag true/false

  15. Offline



    I'm using residence since several weeks and it works great so far. I like it
    My question is now, how can I allow owners of a residence to use TNT but deny the use of TNT to everyone else in this residence?
    I have set global flag of TNT to false, but can not use "/res pset <user> tnt true" because the plugin says "invalid flag". Is there a way to accomplish that without putting every user in an own group and setting the group TNT flag to true?
  16. Offline


    afraid not, it's a 'global' flag, that covers the entire residence, not a per player flag. the tnt flag stops tnt from exploding, not it being placed.

  17. Offline


  18. Offline


    Ah, so I can "/res set tnt true" but keep "/res set build false" as global flag and anyone except the owner can place and blow up tnt. Single "insecure" case would be if the owner places some tnt but does not blow it up - other people will be able to blow this up, right?.
    Can I prevent this maybe with the ignite flag? Or is ignite only affecting fire?

    Thanks for response :)
  19. Offline


    Hello, why I do not properties?? I do not know what they are not open
  20. Offline


    right in both cases. ignite is indeed only for fire and the build flag will stop other players from placing tnt. I'm not sure if other players will be able to detonate it though (if they can, it goes in the same category as paintings, bugged, although i think paintings were fixed.)

    are you unable to create properties? or is the properties file missing? please give more detail. i'm unsure of whats not working.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: Jul 17, 2016
    dompie likes this.
  21. Offline


    OK, I attempted to use this plugin. However the issue I am having is that When I try to create a residence. It tells me the limit is already reached. However I know WITHOUT A DOUBT the configuration file is set properly, and I have tested about 20 different setups to ensure I wasn't mistaken the first time. Same results. When I do the limits commands to find global limits. EVERYTHING is 0 and false. Almost like it isn't taking the settings from the configuration file.

    Note: Im using permissions 2.7.4 i believe is what it is and residence 2.2

    my default group name was untrusted for each world. However when i do the limits it shows group:default or something to that effect. I'm unsure what errors (if any) are popping up as I do not have a console. (using brohoster)
  22. Offline


    post the config, and i'll see if i can help.
    also have you tried it with a 3.x version of permissions to see if it works?
    EDIT: as an attachment/spoiler/paste.bin
  23. Offline


    I am reading you two different ways here. If you want no one to use tnt except owner, set the /res set tnt false. Set the owner default on tnt to true in the config, and /res set tnt false.

    I am not entirely sure if the owner would still have access to tnt but you can also let your user have access to the blacklist for their residence in the config, and let them add it with /res lset itemID and no one can place it.
    dompie likes this.
  24. Offline


    some help (I use last dev build):

    If you want contract your residence from upper edge, you need look upside and use command:
    /res select expand -10 (contract from upper edgo 10 blocks)
    if need contract from other side look this side and use negative value ;)

    For modify Residence
    1. /res select residence <ResidenceID> <AreaID> (if you create simple residence your <AreaID> have name "main". You can see name <AreaID> at /res info <ResidenceID> at Physical Areas as ID:...)
    1.1. /res select coords (verify that are you doing)
    2. do modification (/res select expand, /res select shift, and so on)
    2.1. /res select coords (verify that are you done)
    3. /res area replace <ResidenceID> <AreaID> (<AreaID> - The same name from first step)
  25. Offline


    I refuse to use 3.X as it won't work with some of my plugins. Maybe I missed something in my config by some change i don't know. I'll post more info shortly I need to finish up a few things first.

    Here's the pastebin of the configuration file for residence.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: Jul 17, 2016
  26. Offline


    Any way to change how rentees can't modify the lots they've rented? This PlugIn seems to be the only one that allows me to near-fully automate the Spawn town lots.
    I don't want people to "own" them, but have to frequently (At least once every seven days) have to come in and renew their least.
  27. Offline

    Ross Gosling

    ---> FEATURE REQUEST <---

    Minecart Protection:

    the ability to disable the breaking/placing of a minecart in an area with the exception of admins being able to place and break them.

    Minecart Use:

    if the 'Use' flag is set to true the Mincart can be entered and exited.

    if the 'Container' flag is set to true the Storage Minecart can used.

    if the 'Use' flag is set to true the Powered Minecart can have fuel put into it.
  28. Offline


    It is probably not going to be fixed by using 3.x. I have almost the same issue and am using 3.x.
  29. Offline


    I pasted my config file for anyone if they can help lol.
  30. Offline


    :D I know. I looked, but pasted mine too when I pasted my issue. I can't find a thing wrong with either, but it is a rather large file as configs go, and I tend to not parse well after while. I really think it is simply the plugin doesn't know you don't have a "default" group. I tested it with people in groups "Admin" and "Members" and only I could make a res, most likely because I am not only the only Admin, but also the only OP on the server. I am 90% sure the setup is right.

    The only diff seems to be you getting the message about limits reached. When using the selection tool, we couldn't even get it to give the message about the points being selected properly, which I was getting. So our members aren't even getting messages about it.
  31. Offline


    First off, this is an awesome plugin. I just was wondering if there is a way around the problem I am encountering.

    Problem: I allow many of my users to use WorldEdit's "SuperPickaxe" which lets them mine stuff instantly. Even when I set the destroy/use flag to false for them, they can still break blocks in my residence with the SuperPickaxe. Is there any way I could remove the "worldedit.superpickaxe" permission node in my residence? Or maybe your plugin code could modify the use/destroy flags to support the SuperPickaxe. I just don't want others to be able to break stuff in my residence at all. And I'd rather not disable their SuperPickaxe.

    Oh and by the way, not that it is any big deal, but I am pretty sure when you type "/res lists" the "remove" line reads "remove <listname> - Add a permission list" when it should say "Remove a permission list."

    Again... awesome plugin :)
Thread Status:
Not open for further replies.

Share This Page