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


    Hey guys! thx for this great plugin, got it running on my bukkit server (bukkit 1060, permisssions, essentials, worldguard, residence, worldedit, authme, blift, commandbook, stargate)... only problem i got is with worldedit...
    some users on my server got permissions for worldedit (not adminrights!), and though they have the build false flag in residence set, the still can use worldeditcommands in the residentzones.... is there a way to somehow "bridge" Residence and WE?
    thx for reply
  3. Offline


    I just do it manually, just watchout for the yml structure
  4. Offline


    Why does Residence always break after my server restarts? The only way i can fix it is by replacing the config.yml by a new one. The reason it fails to load Residence is because it cant find the world RolePlay but it exists!
    Here are the errors it gives me:
    [Residence] Found Permissions Plugin!
    2011-09-09 03:48:01 [INFO] [Residence] Failed to load residence (traplolzudead)! Reason:Can't find world:roleplay Error Log:
    2011-09-09 03:48:01 [SEVERE] null
    java.lang.Exception: Can't find world:roleplay
    at com.bekvon.bukkit.residence.Residence.loadYMLSave(
    at com.bekvon.bukkit.residence.Residence.loadYml(
    at com.bekvon.bukkit.residence.Residence.onEnable(
    at com.bekvon.bukkit.residence.Residence.setEnabled(
    at org.bukkit.plugin.SimplePluginManager.enablePlugin(
    at org.bukkit.craftbukkit.CraftServer.loadPlugin(
    at org.bukkit.craftbukkit.CraftServer.enablePlugins(
    at net.minecraft.server.MinecraftServer.e(
    at net.minecraft.server.MinecraftServer.a(
    at net.minecraft.server.MinecraftServer.init(
    2011-09-09 03:48:01 [INFO] [Residence] - Main Save Corrupt, Loading Backup...
    2011-09-09 03:48:02 [INFO] [Residence] Failed to load residence (traplolzudead)! Reason:Can't find world:roleplay Error Log:
    2011-09-09 03:48:02 [SEVERE] null
    java.lang.Exception: Can't find world:roleplay
    at com.bekvon.bukkit.residence.Residence.loadYMLSave(
    at com.bekvon.bukkit.residence.Residence.loadYml(
    at com.bekvon.bukkit.residence.Residence.onEnable(
    at com.bekvon.bukkit.residence.Residence.setEnabled(
    at org.bukkit.plugin.SimplePluginManager.enablePlugin(
    at org.bukkit.craftbukkit.CraftServer.loadPlugin(
    at org.bukkit.craftbukkit.CraftServer.enablePlugins(
    at net.minecraft.server.MinecraftServer.e(
    at net.minecraft.server.MinecraftServer.a(
    at net.minecraft.server.MinecraftServer.init(
    at com.bekvon.bukkit.residence.Residence.loadYMLSave(
    at com.bekvon.bukkit.residence.Residence.loadYml(
    at com.bekvon.bukkit.residence.Residence.onEnable(
    at com.bekvon.bukkit.residence.Residence.setEnabled(
    at org.bukkit.plugin.SimplePluginManager.enablePlugin(
    at org.bukkit.craftbukkit.CraftServer.loadPlugin(
    at org.bukkit.craftbukkit.CraftServer.enablePlugins(
    at net.minecraft.server.MinecraftServer.e(
    at net.minecraft.server.MinecraftServer.a(
    at net.minecraft.server.MinecraftServer.init(
    2011-09-09 03:48:02 [INFO] [Residence] - FAILED INITIALIZATION! DISABLED! ERROR:
    2011-09-09 03:48:02 [SEVERE] null
    java.lang.Exception: Can't find world:roleplay
    at com.bekvon.bukkit.residence.Residence.loadYMLSave(
    at com.bekvon.bukkit.residence.Residence.loadYml(
    at com.bekvon.bukkit.residence.Residence.onEnable(
    at com.bekvon.bukkit.residence.Residence.setEnabled(
    at org.bukkit.plugin.SimplePlu
  5. Offline


    Ok I have done a search. I even googled it, however sometimes Description and even explanations are just real confusing.

    Ok MaxResidences make sense but then there is MaxAreasPerResidence. What is MaxAreasPerResidence? What is meant by physical areas? Does it mean Biomes? Subzones? or even blocks because all that can mean physical areas.


  6. Offline


    Hi, I get the same error, changing LegacyPermissions to true in the config.yml solved it.
  7. Offline


  8. @bekvon , any chance to get a fix for the bugs in the bugs in the lease/rent check cycles that suddenly start to deduct lease/rent without meeting the lease/rent time? Sry for nagging, but our setup is depending on that system!
  9. Offline


  10. Offline



    Everything seems to work fine on the server, but the only problem is that I don't have admin rights! I'm the owner of the server and thus I should automatically be admin, right?

    I've looked in the config file and I don't seem to find how to fix this. I don't have much experience with plugins so it's possible I did something wrong.

    I'd appreciate it if someone could help me with this problem, and eventually give me some tips on how to improve the config file if neccesary :)

    here's the config file:
    #These are Global Settings for Residence.
        # This loads the <language>.yml file in the Residence Language folder
        # All Residence text comes from this file. (NOT DONE YET)
        Language: English
        # Wooden Axe is the default selection tool for Residence.
        # You can change it to another item ID listed here:
        SelectionToolId: 269
        # This determins which tool you can use to see info on residences, default is String.
        # Simply equip this tool and hit a location inside the residence and it will display the info for it.
        InfoToolId: 287
        # 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: 10
        # Allows leases to automatically renew so long as the player has the money, if economy is disabled, this setting does nothing.
        LeaseAutoRenew: false
        # Whether or not to use the Permissions system in conjunction with this config.
        EnablePermissions: false
        # Set to true if NOT using Permissions or PermissionsBukkit, or using a really old version of Permissions
        LegacyPermissions: false
        # Enable / Disable Residence's Economy System.
        EnableEconomy: true
        # The economy system to use (iConomy, MineConomy, Essentials, BOSEconomy, and RealEconomy supported).
        EconomySystem: BOSEconomy
        # Enables or disables the Rent System
        EnableRentSystem: true
        # The interval, in minutes, between residence rent expiration checks (if the rent system is enabled).
        RentCheckInterval: 10
        # Enable or disable residence chat channels.
        ResidenceChatEnable: true
        # Color of residence chat.
        ResidenceChatColor: DARK_PURPLE
        # Whether or not to ignore the usual Permission flags and only allow OPs and groups with 'residence.admin' to change residences.
        AdminOnlyCommands: false
        # Setting this to true makes server OPs admins.
        AdminOPs: true
        # This is the name of the plugin you use for multiworld, if you dont have a multiworld plugin you can safely ignore this.
        # The only thing this does is check to make sure the multiworld plugin is enabled BEFORE Residence, to ensure properly loading residences for other worlds.
        MultiWorldPlugin: MultiVerse
        # Setting this to true causes subzones to inherit flags from their parent zones.
        ResidenceFlagsInherit: true
        # Setting this to false will allow rented residences to be modified by the renting player.
        PreventRentModify: true
        # Setting this to false will cause residence to continue to load even if a error is detected in the save file.
        StopOnSaveFault: true
        # This is the residence name filter, that filters out invalid characters.  Google "Java RegEx" or "Java Regular Expressions" for more info on how they work.
        ResidenceNameRegex: '[^a-zA-Z0-9\\-\\_]'
        # Setting this to true sends a message to the console every time Residence does a rent expire check or a lease expire check.
        ShowIntervalMessages: false
        # These are world flags that are applied when the player is NOT within a residence.
            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
            WorldNameHere: #here you can set flags for individual worlds, these override Global
                #build: true
        # This gives permission to change certain flags to all groups, unless specifically denied to the group.
            move: true
            build: true
            place: true
            destroy: true
            use: true
            container: true
            pvp: true
            tp: true
            ignite: true
            firespread: true
            bucket: true
            flow: true
            lavaflow: true
            waterflow: true
            creeper: true
            tnt: true
            monsters: true
            animals: true
            subzone: true
            healing: true
            piston: true
        # These are default flags applied to all residences from any user group.
            build: false
            use: true
            container: true
            pvp: true
            tnt: true
            creeper: false
            flow: true
            piston: true
            ignite: true
            firespread: true
            piston: true
        # These are default flags applied to the residence creator of any group.
            build: true
            move: true
            use: true
            ignite: true
            container: true
         # These are default group flags applied to a residence made by a user of any group.
            #default: #group name
                #build: true
    # These groups correspond to the Permissions groups defined in your '<worldname>.yml'
        Default: #group name
           # Information about the Residence zone that the player can define.
               # Determins if this group can create residences or not.  This option can be overriden with the permissions node 'residence.create'
               CanCreate: true
               # The maximum number of Residences a player can have.
               MaxResidences: 99
               # The maximum number of physical areas a residence can have.
               MaxAreasPerResidence: 25
               # The maximum number of blocks a Residence can be, East to West (X).
               MaxEastWest: 999
               # The maximum number of blocks a Residence can be, North to South (Z).
               MaxNorthSouth: 999
               # The maximum number of blocks a Residence can be, High to Low (Y).
               MaxUpDown: 128
               # The lowest altitude this group is allowed to protect.
               MinHeight: 0
               # The highest altitude this group is allowed to protect.
               MaxHeight: 127
                # 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: 0
               # Whether or not to allow teleporting to Residences.
               CanTeleport: false
               # Allow or Disallow the use of /res unstuck, to get yourself out of a residence if stuck in one somehow
               Unstuck: true
               # Allow or Disallow the use of the /res select command, if disabled they can only use the selection tool.
               SelectCommandAccess: true
               # Allow or Disallow the group to access the Blacklist/Ignorelist for residences they own.
               ItemListAccess: true
           # Options relating to enter and leave messages on the residence.
               # Whether or not the player can change the Residence enter and leave messages.
               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: You have left %residence.
           # Options relating to the Lease system.
              # The maximum number of days to allow leases.
              MaxDays: 14
              # The number of days to add to the lease following a '/res lease renew' command.
              RenewIncrement: 13
           #Options related to the rent system
               #determines how many residences can be rented by players of this group at once
               MaxRents: 99
               #determines how many residences can be set for rent by players of this group at once
               MaxRentables: 99
           # 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: true
              # The cost, per block, of making a new Residence or adding a area to it.
              BuyCost: 0.1
              # The cost, per block, of renewing a Residence lease (if the lease system is enabled).
              RenewCost: 0.02
           # Flags are checked in the order:
           # 1: Player
           # 2: Group
           # 3: Owner
           # 4: If all others are undefined, reverts to default value (usually true).
           # Flag permissions default to false.
           # These flags settings override the globals.
              # Specifically allow or deny this group from changing certain flags.
                   #build: true
              # Specifys the flags that are applied at residence creation for players of this group.
                  #build: true
              # Specifys the flags that are applied at to the creator at residence creation.
                  #build: true
              # Specifys the flags that are applied to other groups for this residence, at creation.
                   #default: #group name
                       #build: false
              #these flags are applied specifically to this group whenever they are outside a residence
              #these flags will override the flags at the top, under the Global section.
                    Global: #these flags will apply to all worlds
                         #build: false
                    WorldNameHere: #or you can apply them by each individual world
                         #build: false
    # You can manually specify the group a player is in below, this overrides their permissions group.
         player: default
    ItemList: #this is where you can create blacklists / whitelists
         DefaultList: #list name is not important, as long as it is unique. Its good to use a descripive name.
            #type of the list, can be blacklist, whitelist, or ignorelist
            Type: blacklist
            #If you want, you can have this list only apply to one world, otherwise it applys to all worlds
            #World: world
            #You can also have the list apply only to one group, otherwise it applys for all groups
            #Group: default
            #this is the actual list of material names that this list allows or dissallows
            #You can look up the material name by item ID in game by typing /res material <id>
            #Alternativly, you can simply use the item ID in the list, but its less descriptive and harder to see what the list allows or dissallows at a glance
               - 'BEDROCK'
               - 'LAVA'
               - 'STATIONARY_LAVA'
               - 'MOB_SPAWNER'
    # Used to determine which major revision of Residence this config is from, dont change this.
    ResidenceVersion: 2
  11. Offline


    Can I use both the ForSale system and the rent system
  12. I have a logic problem.

    I have big residence, i created subzone, and I sell it to someone, now i would like to remove this subzone because player aren't there any more, i don't have permissions to do that. What can i do?
  13. Offline



    I seem to have a problem with this exact plugin. Whenever it is running on my server it causes everyone to become invincible other than PVP. Is this a bug? or is it a conflict with another plugin?
    Please help. and thanks :)
  14. Offline


    I wanted to take a moment and thank @bekvon for creating this plugin, it is crucial to our server. Currently running it with close to a 1,000 residences (most were automatically generated on a grid system). Thanks!
  15. Offline

    White Sheep

    Can you disable commands in a Residence area?
  16. Offline


    If you are referring to disabling or enabling non-Residence commands, the answer is "No." Sort of... What you are asking for is essentially a residence-based permissions system. That is not to say that it is not impossible. Residence has a well-defined Developer API through which other plugins can define custom residence permission flags that admins and residence owners could set. But the exact implementation would depend on the developer of the command(s)' plugin, not Residence.

    Now, if we could get PermissionsBukkit, bPermissions, or PermissionEx to support residence-based permissions, it would open up some interesting possibilities.
  17. Offline

    White Sheep

    Ok, I have a problem that super-break commands still can demolish a protected area.
    So it is not possible to disable /foo in a area without using the API.
  18. Offline


    Ah. Yes, we have a similar issue with WorldEdit's superpickaxe (//). This is actually something I will be looking at, but right now we are all anxiously awaiting the CB 1.8 release. Most likely, we will be patching WorldEdit to check with Residence and ensure that the player has the +build flag.
  19. Offline


    Also getting this problem, its because a world not set in has res' but I don't know how to fix it. Anyone????
  20. Offline


    Judging from the stack trace, it seems that you have some world-specific configuration(s) in your Residence config.yml. I suggest editing the file and searching for "roleplay". Either delete the world-specific configurations or comment them out if you plan on using the world again in the future or using MultiVerse to offer multiple worlds to your players.

    I'm just guessing here. If you already removed your "roleplay" configurations from Residence's configuration file, you may have to edit its res.yml file and remove/comment any residence that is located in your missing world. Each residence configuration is identified by the residence name and contains several attributes (e.g. EnterMessage, BlackList, LeaveMessage, etc.). Look for any residence that has the attribute World: roleplay and comment out/delete those residence definitions.
  21. I may be Being thicker than a McDonalds milkshake, But what is the purpose of subzones?

    I cant seem to sell or rent subzones, set enter/leave messages for subzones, etc. (i've not even got into flags yet so i have not tested it.

    Also, is it possible to create "admin" residences, I.E. residences that are not owned by anyone, and dont have to adhere to the limits of the plugin?

    Let me give you an example of what i want to do. It probably REALLY simple, but i just cant figure it out, even with watching the video 5 times, and reading the wiki back and forwards over and over.

    One HUGE residence, Called City. Each house in an individual Subsone. Then be able to sell/rent those individual houses. And of course, hopefully use residence signs to do this.

    So basically, one huge protected area, with purchaseable areas within it. Im sure this must be able to be done, otherwise subzones (and or the entire plugin) seems pretty pointless for city based servers. (and I REALLY dont want to use towny)

    Edit: Ok, so i can make residences Server Owned, this is good. But still, can i have sellable Subzones within that? and if so, how do it do it. It dos'nt seem to be anywhere in the command list, and if i try anyway, i get invalid residence.

    Please help, I want to try and get this ready before the new RB of bukkit comes out.

    Thanks in advance

  22. Offline


    any time frame on when this will be working with 1.8?

    "auto-generated"? how?

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


    I just wrote a quick and dirty PHP script that loops adjusting X,Y,Z coordinates and then outputs a YAML Residence config (as well as adding our addressing system but that is a different story). I did this because we have a town world that has a big grid system so each player can have a Residence. You can see what I mean here: Town Map (each square in the roads is a residence, you can click on them to see).

    I have been testing this with 1.8 dev builds and have not found any Residence problems.

    I would recommend just making sure the priority for listening to the events is higher in Residence, and then make sure WorldEdit checks if the event was cancelled before proceeding. This will cause less dependency issues in the future.

    I have fixed this and @bekvon accepted the pull. It will be in the next version.

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


    Good advice, if we're talking about a regular plugin. Take a look at the WorldEdit source and you'll see that the sk89q processes player events to handle superpickaxe function well before they turn into block events. There is no chance of cancelling a block event via Residence, or any plugin, because it never gets created in the first place.
  25. Offline


    Oh thanks for the info :), I am new to Bukkit development so I did not know this.
  26. Offline


    Suggestion: A feature that allows users to create a custom channel with in their Residence. This would allow other users to communicate within the Residence.

    On my server a few users were upset when we switched from Towny to Residence. They no longer had a local channel their residents could use to chat with their neighbors. It would be nice to see a feature that allows this added to the Residence plugin.
  27. No answer to my question? This really is a deal breaker, if I cant do this with residence, there is no point to me using this plugin. Even though I think its great, this is a feature I really need.

    In short, Can I sell/rent subzones? Or indeed can i do ANYTHING with subzones? From my testing they seem completely pointless. Cant sell them, cant put enter/leave messages on them (not even tried flags yet)

    What i need is one large zone that is protected, then many smaller zones inside it, that people can buy or rent.

    i need to know if this can be done in residence, or do i need another plugin along side it? I'd even settle for a quick and dirty work around if anyone knows one. I'd love to be able to sort this before the new RB of Craftbukkit comes out.

    Thanks in advance

  28. Offline


    Of course! You can almost do everything to subzones like to residences.
    You have to use the same command, but to "select" the subzone you have to type <residence>.<subzone>.
    For example the protection of the residence and the allowance to build in the subzone (Example: Residence is called "City" and the subzone "house1")
    /res set City build false
    /res set City.house1 build true
    ouf course, you can set these flags for only 1 permissions group or only for one player.

    The command was successfully, its only an display-issue. I've that too but it anyway is marked for sale.

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

    I seem to now have another issue.

    I sucessfully sold a Subzone, so now my test user is the owner. However, he cannot break blocks or even open chests in that subzone. I know subzones inherit from thier parents, so im guessing as he does not have that access in the main city, he does not have access in the subzone, even though he is the owner.

    Do I have to change the flags on the subzone? Or make a change in the config file? Upon looking through it, i cannot see whats wrong. Obviously I dont want to give break and open commands on the whole city, as that completely defeats the purpose of this entire excercise.

    Never before have i been so confused by a plugin :p
  30. Offline


    Does your config.yml contain something like that:
        # These are default flags applied to the residence creator of any group.
            bucket: true
            build: true
            move: true
            use: true
            ignite: true
            container: true
    If you want me to look into your configfiles (config.yml and res.yml) pm me!
  31. Offline


    Why i am not an admin ?
    Im in the ops.txt file and on the server im [Admin]
    I don't understand why the plugin says im not admin, other plugins works very fine
    I have putted the Onlyopsadmin : true
    Help plz
Thread Status:
Not open for further replies.

Share This Page