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

    bekvon

    MOVED TO DEV BUKKIT:
    [​IMG]
    News

    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

    Links
    Developer API: Wiki
    GitHub Source: GitHub
    DevBukkit Project Page: DevBukkit

    [​IMG]

    Contributors:
    Daniel Few (Wiki)​
    Linaks (Residence Logo)​
    SirHedgehog (Code)
    GSValore (Code)​
    Samkio (Wiki Video)​
    JustinGuy (Code)​

    Addons:
    Residence Signs (by KarnEdge)​

    NOTE: All Residence usage information has been moved to the wiki!

    About:
    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:
    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

    ChangeLog
    v2.4.2
    • Fix bug affecting some people with the new save system
    v2.4.1
    • 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)

    v2.4.0
    • 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...
    v2.3.9
    - 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.

    v2.3.8
    - 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.

    v2.3.7
    • Added direct support for PermissionsBukkit (doesn't go through the bukkit API)
    • Added LegacyPermissions true/false config option.
    v2.3.6
    • 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.
    v2.3.5
    • Fix for firespread flag with CB1000.
    • Added "piston" flag.
    v2.3.4
    • Fixes for CB1000
    • Fixes for a few minor bugs, and for concurrent modification issue with the Lease Manager.
    v2.3.3
    • 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.
    v2.3.2
    • Changed MaxUpDown in the default config to 128...
    • Fixed issue with /res vert still selecting more then the MaxUpDown allowed.
    v2.3.1
    • 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.
    v2.3
    • 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)
    v2.2
    • 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.
    v2.1.3
    • Fixed a couple bugs with the lease system, including being enabled when it shouldn't be and the lease auto-renew option.
    v2.1.2
    • 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.
    v2.1.1
    • Fix case sensitivity bug in rent system.
    v2.1
    • 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 :)
    v2.0
    - 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

    bekvon

    Update:
    Things are comming along rather well as of now :) Heres a brief list of things that have been added to the development version if anyone wants to test them:
    • BOSEconomy support, needs testing.
    • Essentials economy support, needs testing.
    • 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.
    • Probably some other minor things I've forgot :)
    I will be taking a brief break from coding this after the stable release of 2.1, and will be paying a bit of attention to my other plugins, and of course real life stuff as well. :)


    Theres BOSEconomy support in the development version right now, however its untested. If your brave enough, give it a go :) You'll need to change your economy setting the the config to BOSEconomy.
     
  3. Offline

    Nlioc4

    Testing the BOSEconomy version now :D Thanks :D So far no errors, working great. I use your plugman plugin as well, thank you for both of them :)
     
  4. Offline

    Avous

    @bekvon everything on the dev build works great so far! one thing. can you set the TP location of residence? i cant find the command
     
  5. Offline

    GmK

  6. Offline

    zionite

    This is by far one of the nicest plugins i've used. Great work!

    I'm having an issue though, running iConomy. I create residences just fine, but it doesn't deduct money from my account. What is the fix? Or am I misunderstanding how it works?

    I'm on craftbukkit 766, Residence 2.0, iConomy 5.01

    EDIT: Ok, so it just isn't charging me because I'm the admin. Other accounts are being charged. How can I be charged as an Admin?

    Also, while crops can't be destroyed by your guests' hands or tools, walking on top of crops still decays them enough to break them down. I'm assuming this shouldn't happen.
     
  7. Offline

    Blobinet

    Whenever a player from the default group does a right-click, they get the message "You don't have permission do use this"

    Here is my config file :
     
  8. Offline

    Cannoisseur


    I use latest recommended build.

    My original comment:
     
  9. Offline

    Daniel Few

    Yes I think this is a bug atm as I am getting it to. However Bekvon should soon be ready for a new update I think and I'm sure he knows about this problem :).
    -DanJames
     
  10. Offline

    Nytemare3701

    @bekvon
    Can I get a confirmation that you saw these?
     
  11. Offline

    chicagosandman

    This still allows them to place water/lava blocks does it not? I mean not even being able to do that.
     
  12. Offline

    Daniel Few

    Oh yes it enables them to still 'place' the blocks, but they will not flow. To stop them being placed, see the 'Item Blacklisting' at the bottom of the config file.
    -DanJames
     
  13. Offline

    Zixt

    Is there a way Residence can override WorldGuard restrictions on use restrictions?
     
  14. Offline

    ThatGuy295

    Hey, I can't seem to put a 'valid' price to sell.
     
  15. Offline

    chicagosandman

    Are you saying I should blacklist a water block? Or just the water bucket. And what exactly does blacklisting do?
    Thanks for the tip, I will look into this...
     
  16. Offline

    Daniel Few

    There are two types of lists.
    Whitelist=blocks everything except things listed
    Blacklist=enables everything except the things listed
    In the case of residence, you can have a blacklist which blocks certain items from being used.

    Are you players able to access the water/lava block. Eg. do they have a give command.
    If the answer is yes, you will want to block the water block, flowing water, lava block, flowing lava, water bucket and lava bucket. You may also want to blacklist the bucket to stop them collecting water themselves.
    If the answer is no, they can not give, then all you need to do is block the water/lava bucket and the bucket itself.

    If you need more information please ask :)
    -DanJames
     
  17. Offline

    Junrall

    Wow!
    A very cool plugin! And easy to set up!! Which is great as I am in the process of setting up my first online server.

    If I can throw in my two cents...
    Is it possible to incorporate an option that allows players to place a specific block type and have it create a predetermined sized area? The predetermined size could be set in the config file and would specify the distance outward from the block in all directions. So, a block set to 10x10x10 would create a resident area size of 21x21x21. Once the block is placed the player could then set properties the same as if they had chosen two corners. Also, lets say that the block was made of iron... this would force people to "work" for protection. Or rather than a block just create another tool that does this when used. What makes this appealing to me is that you wouldn't have to create a pillar just to set an upper selection point.

    Another idea would be to allow players to overlap the edges of multiple areas. All areas created after the first area would inherit the enter/exit messages... messages would not be displayed if someone crosses over the overlapped edges.

    Also, a couple of things about the current version:
    First... will "select vert" override the MaxUpDown setting? If it does, should it?
    Second... what are some limitations I should be aware of... such as setting MaxResidences too high or too many people setting "select vert".... specifically that cause the server to crash or lag.

    Thanks!
     
  18. Offline

    Daniel Few

    This can be done now with the /res area add command.
    1. Set up a residence with '/res create <residence>'
    2. Give it the flags you want using '/res set <residence> <flag> <true/false>'
    3. Create a second cuboid either directly next to, overlapping or far away from your first residence.
    4. Use the '/res area add <residence> <areaID>' command. The areaID can either be a number or a name and is just used to identify the different areas. The main residence area's idea will be 'main'.

    These areas will inherit all properties from the original residence and if you change any options in any of the areas they will be transferred to all other areas. This option allows you to create more complex selections other then a cuboid.

    If the residence's are directly next to each other, as you cross over the residence the enter/leave message will not be posted. However it will be if they are in different places.
    As i said above, this can be used to create the same residence in mulitple areas. Eg. you could make a shop residence and then give all your shop the same residence areas to show the same enter/leave message.

    One thing to mention is that all these areas will be the SAME residence, they are not separate ones.

    Hope this helped,
    -DanJames
     
  19. Offline

    WizardCM

    Would love more Permissions than residence.admin... otherwise, awesome plugin!
     
  20. Offline

    Daniel Few

    The whole residence plugin works around it's own config.yml file. You can set up many different permissions in there to make the plugin run exactly as you want it to.
    There is much more control doing it the way bekvon has done it then if he did it with permission nodes as youn can set up specific rules.

    Although, the question is what would you like to see?
    -DanJames
     
  21. Offline

    WizardCM

    Well the ability to set up the permissions through Permissions instead of Residence would be nice. For example, when I first used this plugin I didn't realise Residence controlled PvP on all worlds, which meant mobs couldn't be killed. Took me a week to figure out it was Residence's fault. :p
    Also, would be great if there was an option to set Residence's world permissions to only be used on worlds with residences.

    Would be great if the Wiki held more information, and was a little more organised, too.
     
  22. Offline

    Atticus Craft

    Can we get an option to change the error text? Like when someone doesn't have permission to do something or enter a protected area, can we change that text (on a per residence basis?)
     
  23. Offline

    Daniel Few

    Can you suggest how the wiki can be more organised? Obviously it's not finished yet but I thought I made it as clear as possible. But if you have a suggestion please tell us.
    I can't speak for bekvon, but I wouldn't have thought residence could work all with permissions nodes as you need the in death and specific settings like what happens when you create a residence, what flags are applied, what happens when you delete a residence.
    Do you just mean say one for allowing them?
    -DanJames
     
  24. Offline

    Avous

    @bekvon out of curiousity. can you expand a residence after its made?
     
  25. Offline

    Daniel Few

    Yes, once you've made a residence, use the '/res area add' to add multiple areas to that residence. This is NOT subzones. It adds new cuboided areas to the original main zone. See my post above.

     
    AlsoKnownAsJazz likes this.
  26. Offline

    bekvon

    Hmm, I'm not sure if this is a bukkit issue or a Residence issue, I'll try to research it when I can.

    Hmm, this is a bug I fixed a while back (before 2.0 stable even I think), and I'm not getting it on my end anymore, are you guys using 2.0 stable? Also, it couldn't be that you have 'use' set to false for your world flags?
    The /res select command selects around you using you as the center point, that means you don't need to hit F3 and type in coordinates from there, just do something like /res select 5 5 5, which will select 5 blocks in all directions from where your standing.

    The reason I don't use Permissions to much is that it has limitations. For example, you can't have the permission node 'residence.default.entermessage = "Hi this is a residence"' Rather then split everything halfway between Permissions and Residence, I opted to put everything in my own config file. Also, you can set Residences World permissions on a per world basis in the config. :)

    I'll eventually be moving all in-game messages outside to a separate config file, but its a low-priority thing at the moment. I;m also going to be moving the ingame-help system to a separate help config file here, which will probably happen sooner. :)

    Using the /res area commands you can add more cuboids to a residence. However, a strait up re-size isn't possible at the moment. However, its a good idea and I can probably implement it in the future :) It would charge you the difference in size between the two areas, so you wouldn't end up wasting money.
     
  27. Offline

    klaxer

    Sorry for dumb question, can't find answer by myself.

    I want to create two group : Newbies and Members. I want to allow Members build in all residences. How it can be done? Looks like i need to change section
    Code:
    # Specifys the flags that are applied to other groups for this residence, at creation.
    GroupDefault:
    #default: #group name
    #build: false
    but without an example i can't do this in right way:(
     
  28. Offline

    RobotGymnast

    Excellent, excellent plugin! All the configurability I've been looking for (and more).
     
  29. Offline

    Atticus Craft

    What would it take for you to consider increasing the priority on this? It totally ruins the mood for the world, where everything else has nice, rpg themed messages, and this one is so 21st century :)
     
  30. Offline

    1Toad1995

    I finished editing and got it working how I wanted... Then I found out whenever a non-moderator+ tries using the /res command it says: "Only admins have access to that command". I looked all through the config file and couldn't find an answer and there is no permission node for it. Does anyone know how to fix it? If it helps here is my config file:

    Code:
    #These are Global Settings for Residence.
    Global:
        # Wooden Axe is the default selection tool for Residence.
        # You can change it to another item ID listed here: http://www.minecraftwiki.net/wiki/Data_values
        SelectionToolId: 280
        # 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: Standard
        # 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: true
        # Whether or not to use the Permissions system in conjunction with this config.
        EnablePermissions: true
        # Enable / Disable Residence's Economy System.
        EnableEconomy: true
        # The economy system to use (iConomy, MineConomy, Essentials, and BOSEconomy supported).
        EconomySystem: iConomy
        # Enables or disables the Rent System (NOT FINISHED YET!)
        EnableRentSystem: true
        # The interval, in minutes, between residence rent expiration checks (if the rent system is enabled).
        RentCheckInterval: 10
        # Whether or not to ignore the usual Permission flags and only allow OPs and groups with 'residence.admin' to change residences.
        AdminOnlyCommands: true
        # 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
        # These flags are applied when the player is not within a residence.
        Flags:
            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: false
            WorldNameHere: #here you can set default flags for individual worlds, these override Global
                #build: true
            # This gives permissions for certain flags to all groups, unless specifically denied to the group.
        FlagPermission:
                move: true
                build: true
                use: true
                ignite: true
                pvp: true
                tp: true
                flow: true
                firespread: true
                creeper: true
                tnt: true
                container: true
                place: true
                destroy: true
    
    # These groups correspond to the Permissions groups defined in your '<worldname>.yml'
    Groups:
        Standard:
           # Information about the Residence zone that the player can define.
           Residence:
               # Determins if this group can create residences or not.  This option can be overriden with the permissions node 'residence.create'
               CanCreate: false
               # The maximum number of Residences a player can have.
               MaxResidences: 1
               # The maximum number of physical areas a residence can have.
               MaxAreasPerResidence: 100
               # The maximum number of blocks a Residence can be, East to West (X).
               MaxEastWest: 100
               # The maximum number of blocks a Residence can be, North to South (Z).
               MaxNorthSouth: 100
               # The maximum number of blocks a Residence can be, High to Low (Y).
               MaxUpDown: 256
               # The lowest point this group is allowed to protect.
               MinHeight: 0
               # The highest point 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: true
               # Allow or Disallow the use of /res unstuck, to get yourself out of a residence if stuck in one somehow
               Unstuck: true
           # Options relating to enter and leave messages on the residence.
           Messaging:
               # Whether or not the player can change the Residence enter and/or leave message.
               CanChange: true
               # The default enter message to apply to new Residences created by players in this group.
               # Leaving the message blank will disable it.
               DefaultEnter: Welcome %player to %residence, owned by %owner.
               # The default leave message to apply to new Residences created by players in this group.
               # Leaving the message blank will disable it.
               DefaultLeave: Now leaving %residence.
           # Options relating to the leasing of zones.
           Lease:
              # The maximum number of days to allow leases.
              MaxDays: 10000
              # The number of days to add to the lease following a '/res lease renew' command.
              RenewIncrement: 14
           #options related to the rent system
           Rent:
               #determines how many residences can be rented by this group at once
               MaxRents: 10000
               #determines how many residences can be set for rent by this group at once
               MaxRentables: 10000
           # Options relating to the Residence Economy.
           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: false
              # Whether or not to ignore the Residence size/count limits when buying a residence.
              IgnoreLimits: true
              # The cost, per block, of buying a Residence or adding a area to it.
              BuyCost: 0.1
              # The cost, per block, of renewing a Residence lease.
              RenewCost: 0.05
           # Flags are checked in the order:
           # 1: Player (in-game only)
           # 2: Group
           # 3: Owner
           # 4: Default
           # 5: Otherwise, if all others are undefined, defaults to 'true'.
           # Flag permissions default to false.
           Flags:
              # Specifys the flags that players of this group are allowed to change.
              Permission:
              # Specifys the flags that are applied at residence creation for players of this group.
              Standard:
                   build: true
                   use: true
                   tnt: false
                   pvp: false
                   creeper: false
                   firespread: false
                   container: true
              # Specifys the flags that are applied at to the creator at residence creation.
              CreatorDefault:
                   move: true
                   build: true
                   use: true
                   container: true
              # Specifys the flags that are applied to other groups for this residence, at creation.
              GroupDefault:
                   #default: #group name
                       #build: false
              #these flags are applied to this group whenever they are outside a residence
              #these flags will override the flags at the top, under the Global section.
              World:
                    Global: #these flags will apply to all worlds
                         #build: false
                    WorldNameHere: #or you can apply them by each individual world
                         #build: false
        Moderator:
    # Information about the Residence zone that the player can define.
           Residence:
               # 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: 10000
               # The maximum number of physical areas a residence can have.
               MaxAreasPerResidence: 20000
               # The maximum number of blocks a Residence can be, East to West (X).
               MaxEastWest: 100
               # The maximum number of blocks a Residence can be, North to South (Z).
               MaxNorthSouth: 100
               # The maximum number of blocks a Residence can be, High to Low (Y).
               MaxUpDown: 256
               # The lowest point this group is allowed to protect.
               MinHeight: 0
               # The highest point 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: 5
               # Whether or not to allow teleporting to Residences.
               CanTeleport: true
               # Allow or Disallow the use of /res unstuck, to get yourself out of a residence if stuck in one somehow
               Unstuck: true
           # Options relating to enter and leave messages on the residence.
           Messaging:
               # Whether or not the player can change the Residence enter and/or leave message.
               CanChange: true
               # The default enter message to apply to new Residences created by players in this group.
               # Leaving the message blank will disable it.
               DefaultEnter: Welcome %player to %residence, owned by %owner.
               # The default leave message to apply to new Residences created by players in this group.
               # Leaving the message blank will disable it.
               DefaultLeave: Now leaving %residence.
           # Options relating to the leasing of zones.
           Lease:
              # The maximum number of days to allow leases.
              MaxDays: 10000
              # The number of days to add to the lease following a '/res lease renew' command.
              RenewIncrement: 14
           #options related to the rent system
           Rent:
               #determines how many residences can be rented by this group at once
               MaxRents: 10000
               #determines how many residences can be set for rent by this group at once
               MaxRentables: 10000
           # Options relating to the Residence Economy.
           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 buying a Residence or adding a area to it.
              BuyCost: 0.1
              # The cost, per block, of renewing a Residence lease.
              RenewCost: 0.05
           # Flags are checked in the order:
           # 1: Player (in-game only)
           # 2: Group
           # 3: Owner
           # 4: Default
           # 5: Otherwise, if all others are undefined, defaults to 'true'.
           # Flag permissions default to false.
           Flags:
              # Specifys the flags that players of this group are allowed to change.
              Permission:
              # Specifys the flags that are applied at residence creation for players of this group.
              Moderator:
                   build: true
                   use: true
                   tnt: false
                   pvp: false
                   creeper: false
                   firespread: false
                   container: true
              # Specifys the flags that are applied at to the creator at residence creation.
              CreatorDefault:
                   move: true
                   build: true
                   use: true
                   container: true
              # Specifys the flags that are applied to other groups for this residence, at creation.
              GroupDefault:
                   #default: #group name
                       #build: false
              #these flags are applied to this group whenever they are outside a residence
              #these flags will override the flags at the top, under the Global section.
              World:
                    Global: #these flags will apply to all worlds
                         #build: false
                    WorldNameHere: #or you can apply them by each individual world
                         #build: false
        Owner:
    # Information about the Residence zone that the player can define.
           Residence:
               # 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: 10000
               # The maximum number of physical areas a residence can have.
               MaxAreasPerResidence: 200000
               # The maximum number of blocks a Residence can be, East to West (X).
               MaxEastWest: 10000
               # The maximum number of blocks a Residence can be, North to South (Z).
               MaxNorthSouth: 10000
               # The maximum number of blocks a Residence can be, High to Low (Y).
               MaxUpDown: 256
               # The lowest point this group is allowed to protect.
               MinHeight: 0
               # The highest point 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: 100
               # Whether or not to allow teleporting to Residences.
               CanTeleport: true
               # Allow or Disallow the use of /res unstuck, to get yourself out of a residence if stuck in one somehow
               Unstuck: true
           # Options relating to enter and leave messages on the residence.
           Messaging:
               # Whether or not the player can change the Residence enter and/or leave message.
               CanChange: true
               # The default enter message to apply to new Residences created by players in this group.
               # Leaving the message blank will disable it.
               DefaultEnter: Welcome %player to %residence, owned by %owner.
               # The default leave message to apply to new Residences created by players in this group.
               # Leaving the message blank will disable it.
               DefaultLeave: Now leaving %residence.
           # Options relating to the leasing of zones.
           Lease:
              # The maximum number of days to allow leases.
              MaxDays: 10000
              # The number of days to add to the lease following a '/res lease renew' command.
              RenewIncrement: 14
           #options related to the rent system
           Rent:
               #determines how many residences can be rented by this group at once
               MaxRents: 10000
               #determines how many residences can be set for rent by this group at once
               MaxRentables: 10000
           # Options relating to the Residence Economy.
           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 buying a Residence or adding a area to it.
              BuyCost: 0.1
              # The cost, per block, of renewing a Residence lease.
              RenewCost: 0.05
           # Flags are checked in the order:
           # 1: Player (in-game only)
           # 2: Group
           # 3: Owner
           # 4: Default
           # 5: Otherwise, if all others are undefined, defaults to 'true'.
           # Flag permissions default to false.
           Flags:
              # Specifys the flags that players of this group are allowed to change.
              Permission:
              # Specifys the flags that are applied at residence creation for players of this group.
              Owner:
                   build: true
                   use: true
                   tnt: false
                   pvp: false
                   creeper: false
                   firespread: false
                   container: true
              # Specifys the flags that are applied at to the creator at residence creation.
              CreatorDefault:
                   move: true
                   build: true
                   use: true
                   container: true
              # Specifys the flags that are applied to other groups for this residence, at creation.
              GroupDefault:
                   #default: #group name
                       #build: false
              #these flags are applied to this group whenever they are outside a residence
              #these flags will override the flags at the top, under the Global section.
              World:
                    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.
    GroupAssigments:
    
    ItemList: #this is where you can create blacklists / whitelists
         ListName: #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 or whitelist
            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
            Items:
    
    # Used to determine which major revision of Residence this config is from, dont change this.
    ResidenceVersion: 2
     
  31. Offline

    Avous

    @bekvon
    Great! I have one more request if you're up to it. can you make Wolves immune to damage with damage (false)? people on my server are having their wolves killed when the players are AFK​
    And before I forget... .... i forgot what i was gonna say i hate when that happens...​
    ... REMEMBERED!... (after i closed the browser... typical)​
    Buckets! people can use and place bucket contents anywhere.​
    I dunno if its because of "Use" but it should be under Place/build
     
Thread Status:
Not open for further replies.

Share This Page