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


    Man, this is awesome, Residence has been developed so much since tha last time I was here!
    Haven't tried the latest version yet... Are doors working now?

    Also, gratz, you've done an excellent work here, I'd donate if I could =/
  3. Offline



    First I'd like to thank you for the great plugin.

    And secondly, I have an unanswered question:

    When I set flags to authorize teleportation (/res set tp true or /res pset player tp true), the players should be able to teleport. But...they can't. The permission is denied, the flag is working though.
    In the permissions configuration file, unless I give them all commands (using '*') I don't know how to allow them to teleport.

    This is extremely fustrating, as I wish for all my players to be able to teleport to their residences.
    Any help would be greatly appreciated, and a donation will follow (in all cases).

    Thanks again,
    Keep up the great work!
  4. Offline


    Not at the moment, Il make it possible in the future though as that shouldn't be to hard :)

    Doors arent working yet, as its a bukkit issue actually. Probbably they will have it sorted in the next recommended build :)

    Oh yea, I forgot to put in the change log. It used to be a permission, but its been moved into the config.yml. Under each group there is a tpAccess true/false flag that you have to enable. And um... I think I just realized that its backwards with v1.2.... allows if its set to false and denys on true.... I'll fix that :D And thank you, all donations area very much appreciated :D
  5. Offline


    This may have been addressed but is it possible to migrate/update old region protections to the Residence zones according to membesr/owners registered on each zone (I'm talking about worldedit regions)? Or would we have to protect everything over again?
  6. Offline


    I'm not sure if it's fixed, but I realized what the issue was with creating subzones. If you are standing inside of a Residence, and attempt to create a subzone by explicitly stating the name of the residence you are in, then the command doesn't work.
    /res subzone ResName SubZoneName
    however this does work: /res subzone SubZoneName

    It's as if, because you are inside of the residence then it doesn't check for proper arguments.
  7. Offline


    Hi ya i don't know if its a bug or not but its really infuriating me. When i have created a residence it seams that people that have the default permissions i.e. only have the - 'residence.create' permission, can't place blocks in protected zones as expected but they can still dig them up, i have had exactly the same problem with other plugins such as WorldGuard and iZone. but the thing that has stumped me most of all is that when i '/reload' the server plugins and all of a sudden players can't dig up blocks, it fixes the problem. Unfortunately at the same time it stuffs up other plugins. Any advise on this mater would be of great help. Its probably something daft i have done but its driving me crazy! lol

    Thanks, Pipster121.

    BTW server ip is if any one wants to come in and have see what i mean.
  8. Offline


    I just wanted to say that this plugin is almost the answer to my hopes, prayers, and dreams.

    If you could find a way to, possibly through another plugin that extends the functionality of this one, to have all of the useful town/nation features of towny coupled with your excellent block based regioning, I really think you'd find alot of faithful Towny users jumping ship, I know I would.

    Very well done overall, I will be keeping my eye on this thread.
  9. Offline


    Is it possible to protect paintings when the build flag is set to false? Up to yet others can destroy paintings which is really annoying. Is this maybe connected with the use flag? Isn't it the same algorithm like surface objects (torches)?

    Next it would be great if you add a flag for enter/leave messages itself to prevent chat spam in cites.
    Now its only possible to set the Message but the name of the residence is still shown when the string is empty.

    Last to prevent overlapping in cities, the form of residences (now as rectangle) has to been smoother. This can be reached through connecting of zones to 1 zone. The player entered/leave check would be realized through a super class (the whole zone) and subclass which are the single zones, so the check would be check every sub zone and get the enter/leave message from the parent zone. It's not the same like the sub zones now because this sub zones has to be in the range of the parent zone and can't be a expansion, or is this already possible?
    This is only a suggestion how to do it because I don't know how you realized the check and select algorithm yet.

    If you won't change it in the next time, you could send me the source code and I will do it by myself.
  10. Offline


    Hey I told you about the missing pvp worldflag, could you also add a global monsters flag, like for residences?
  11. Offline


    Vake that's peacefull difficulty anyway.
  12. Offline

    kyle hickson

    when a player tries to buy a land it says unable to get iconomy accounts please help
  13. Offline


    Would it be possible to make a permission that only allows players to buy or sell land, not create it?
    This way towns could be set up, and enforced as the main places to live, because people would have to buy a plot, not create their own.
    I'm looking for an alternative to towny, and if you could implement this idea, this would definately replace towny.
  14. Offline


    Sry I forgott....

    Changed it my post ^^
  15. Offline


    The new way to setup permissions seems powerful, but it is not intuitive AT ALL. There are way too many options now that seem like they do the same exact thing, or are just plain confusing. I imagine it allows for a lot more customization, but I feel that it is unnecessarily complicated.
    Identity62 likes this.
  16. Offline


    It's me again!
    You got me confused with the inverting here,
    could you take the time to tell me if this config file should enable VIP group to teleport ?

        use: true
        build: true
        tp: true
            maxX: 50
            maxY: 256
            maxZ: 50
            maxPerPlayerResidences: 4
            costPerBlock: 0.03
            tpAccess: false
                move: true
                use: true
                build: true
                pvp: true
                fire: true
                damage: true
                explosions: true
                monsters: true
                tp: true
                use: false
                build: false
                pvp: false
                tp: true
                use: false
                build: false
                move: false
                tp: true
                move: true
                use: true
                build: true
                admin: true
                tp: true
                build: true
                use: true
                tp: true
    I also have a small request, could you document exactly what the flag 'groupments' do? As I don't know what the difference in between flagaccess and playerflagaccess would be...

    Thanks again!
  17. Offline


    How do I mark an area with my wood axe and not by /res select X Y Z ? It dont work when just right-clicking on two spots with my wood axe.. How do I do? Plz help :D
  18. Offline


    It's a left click ;)
    Left click one corner and then right click a second corner (trace a diagonal) and it should work. If not sure type in:
    /res select size

    Best of luck !
  19. Offline


    I'm really interested in adopting this - but cant until the perm nodes get resolved.

    Good headway though! interested to see how it continues to play out.
  20. Offline


    But it doesnt work :S Ill try reinstalling the plugin.

    Still wont work! :S What's wrong?

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


    Maybe I missed it, but is there a way to allow 2 or more people to own/work in the same protected area without letting anyone else touch anything? I couldn't find anything last night so I switched back to Towny temporarily (because iZone doesn't allow multiple users either).
  22. Offline


    You mean convert worldguard to residences? might be possible

    Should be fixed now, It was a simple chat parsing error.

    Are you running iZone, WorldGuard, and this all at the same time? Seems like you might have a plugin conflict with another plugin, you may want to try to removing some other plugins temporarily to see if it fixes it.

    I have thought of things like that, but if I did them, then yea it would definably be through a different plugin.

    I wouldn't be surprised if that destroy bug wasn't for the same reason doors aren't working now. The bukkit team is playing around with events and changing things, and the next recommended build is probably going to break alot of plugins, including this one (of course I'll update it).

    And yea, Il put in a leave/enter flag, that's probably the best solution. Also, it determines your current area by a simple single function (which also caches your current area), and there's no super class involved. The primary zone and subzones are all the same class. Also, subzones have to be in within the parent area, they cant go outside.
    What version of iConomy are you using? I may need to update to the newest, been working with 4.5.2.
    You can do this right now I think. There's a allowSell and allowBuy under the config file that you can set to true, and then you can not give the person the "residence.create" permission.

    I know, they are a bit confusing, im trying to figure out how to simplify them.

    Set tpAccess to true now. I fixed the whole inverting thing. Looks like you got it all right except the tpAccess which is what actually gives them access to the tp command. As for groupments, it basically determines which flags the person has access to. Heres what they do, playerflagaccess is all flags that the user can set for a individual player on his residence(s), where as groupflagaccess is flags that are allowed to be set on groups, and flagaccess is the flags that are allowed to be set globally on his residence(s). So for example, if I have "build: true" and "move: false" under flagaccess, I am allowed to do "/res set <residence> build true" but am not allowed to do "/res set <residence> move true", because I don't have access to that flag. groupflagaccess works the same way except for the "gset" command instead of the "set" command. playerflagaccess is for the "pset" command.

    I hope this makes sense, as I do realize its kinda confusing and prolly needs to be changed hehe....

    You might have a bad bukkit build, make sure your using 556.

    What perm nodes specifically do you need? All the things in the config are just like perm nodes since they work by group too.

    Well, only one person owns it, but if he wants to let somone else build he can do "/res pset <residence name> <player> build true" to allow them to build, and "/res pset <residence name> <player> use true" to allow them to use chests/furnaces, etc...

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


    It's amazing :(
    at com.bekvon.bukkit.residence.Residence$
    at com.bekvon.bukkit.residence.Residence.access$300(
    at com.bekvon.bukkit.residence.Residence.saveYml(
    at com.bekvon.bukkit.residence.managers.ResidenceManager.getYamlCompatible(
    > 22:26:55 [SEVERE] null
    > 22:26:55 [INFO] [Residence] - Save CORRUPTED: java.lang.NullPointerException 
    This is the Log if the autoSaveInterval begins.
    What's the problem?
  24. Offline


    Two things:

    One, the subzone issue you believe was fixed that you addressed above is NOT.

    Two, is there a way to disable entry/exit messages all together for only specific zones? Let's say someone wants to protect a residence, but keep it hidden like a base - having a welcome message isn't very effective.
  25. Offline

    Josh Harwood

    can you make permissions nodes to allow me to set donors to tp to their residences, stop pvp, heal users etc etc
    i want to have regular users be able to only protect the area from building
    then ahve donors allowed to stop people fighting and heal users and stuff
  26. Offline

    Nat Ryall

    Is there a way to disable the message for a particular zone? A configurable flag (named message) would be great.
  27. Offline


    Ok, I'll take another look at the subzones, I really thought it was fixed :oops:
    And yea, I'll go ahead and make a way to remove the welcome message, lots of people have been asking for it.

    You can do all of this in the config file. The config file has a "groups" section. Under each group there is a tpAccess setting that you can change to true or false to give permission to teleport to residences. The group a user is in is the same group as their permission group. So if they are in the "vip" group in permissions, they will be in the "vip" group in my config as well. You can also set what flags they have acess to in the config file, I know its a bit confusing right now, I want to eventually clean it up a bit.

    Yea, I'm going to put that in there :)
  28. Offline


    This Does Not go With Towny
  29. Offline

    Nat Ryall

    Disabling fire globally gives me this exception every 10s or so:
    [SEVERE] Could not pass event BLOCK_IGNITE to Residence
            at com.bekvon.bukkit.residence.listeners.ResidenceBlockListener.onBlockIgnite(
            at org.bukkit.plugin.RegisteredListener.callEvent(
            at org.bukkit.plugin.SimplePluginManager.callEvent(
            at net.minecraft.server.BlockStationary.a(
            at net.minecraft.server.World.h(
            at net.minecraft.server.World.g(
            at net.minecraft.server.MinecraftServer.h(
    It might be coming from my lava structures.
  30. Offline

    Josh Harwood

    so let me get this straight... your plugin interfaces with permissions to let permissions set if a user can use residence or not, and then implements it's own permissions type system instead of implementing support for permissions properly? i really hope that is cleaned up soon :S
  31. Offline


    Is there a way to remove or change the coordinates of the residence once created from in game for the default player? Like if a player doesn't fully get the cube selection and wants to make a change in game.
Thread Status:
Not open for further replies.

Share This Page