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


    Yea, ok that does sound more like a conflict of plugins problem now. Hmm, I would imagine that its a conflict between this plugin and some other plugin that tracks player movement in some way. Could be another protection plugin or could be somthing else, im not sure. Can you PM me a list of the plugins you use?

    All tnt and creepers within the area should'nt explode at all. I haven't actually added a flag to enable them yet, but i plan to. The damage flag means that all damage from zombies / skeletons / monsters is disabled. The mob flag simply prevents them from spawning in the area.
  3. Offline


    This plugin works great no issues except one.

    When making an area, once selevted and /res create name it works, but does not take away from your iconomy cash. i tested this extensively with and without admin status.

    I have essentials group manager, newest iconomy, newest recommended bukkit build as of today.
  4. Offline


    Really great plugin! Though, as many other atm, I'm having trubles with areas showing up in listing but you can't enter them or do anything with them :p But will keep a close watch on the development here ^^

    Ohh and btw, is there any way yet to change the tool you set the area with?
  5. Offline


    greeat looking plugin will be testing this later :)

    with regards to iconomy would it be possible to have an option for upkeep on protected areas? maybe every x number of days players are charged to keep their protection?
  6. Offline


    I noticed someone asked about doors. I would assume you are affected by the same bukkit bug/issue (apparently they are changing to code for interacting with blocks) that is affecting LWC as well. Apparently some of the door handling code was changed and not allowing doors to be protected. Here is the relevant post in the LWC thread:

    And apparently this is the bug report for bukkit:
  7. Offline


    Realy great plugin. Thanks.
    But i have a questing to you.
    No one can walk into my area. Yes, i can give a access using commands but how can i give permission to everyone to every area on the default?
  8. Offline


    Hello i have made an arena and i dont ppl to destroy it and this work perfect! But it is 1. When players play pve against zombies that i spawn so does not creeper explodes in there i want them to explode not so they destroy the arena i tried to disable Fire but it still dosnt work :/ I tried with a tnt and it did blow up a big hole but after 5 seconds the hole auto repaird, i want the same thing to happend to the creeper it explode and damage the player but not the arena :)
  9. Offline


    hi, just created a server and this is a really nice plugin, but I need a lil help. Is there a way to --restrict- players from building outside their plot? I've tried worldguard but I dont see anyway to restrict the size of the plot like your "limit" does.

    tldr. restrict players from building outside thier plots?
  10. Offline


    I just release v1.1.1 - BETA. Notice the word "BETA." LOTS of changes. The config file is completly different and waaay more modular. Tons of new features too. I expect there are still some bugs in this version, but I need help testing everything as its hard to test this all by myself :)

    Try the new version, I changed some stuff and hopefully it should work now. Let me know if it doesnt.

    Possibly, kind of like Towny does. I can implement that, but it may be a while as there is still lots to be done.

    Not right now there isnt, but I added that to the ToDo list. Il make a default build permission somewhere in the config file.
  11. Offline


    I see you just added that as I posted hehe, ty ty ty!!
  12. Offline


    I forgot to mention, as of 1.1 all protections are now OFF by default unlike in the previous version.
  13. Offline


    Think you could make it prefix the (lowercased version of) a player's name to the zones? Then it could automatically prefix it when they use a command, whereas admins could have a flag on the command itself (-f for -full?) to access/modify that player's residence.

    This would allow everyone to name their residence 'home' if they so wished.

    If I misunderstood how this works please feel free to correct me :3
  14. Offline


    v1.1.2 fixes a couple bugs I found while testing.

    While its a good idea, it could get confusing. If I have a zone named home and my friend has a zone named home, and I give my friend admin access to my zone and then he goes to change a flag, it wont know which "home" he is trying to change it on (his or mine).
    Jfed likes this.
  15. Offline


    Hmm, you could have the -f flag for everyone to use then?
  16. Offline


    Toss in MySQL support to keep the list of coords, and you will be my best friend. I am also tired of Towny's clumsiness (and the fact that /plot forsell never seems to work), and am looking for a more streamlined way to allow my players to protect their buildings.
  17. Offline


    Amazing plugin. I've been watching this for a few days now and I'm definitely impressed by the progress you've made in such a short time.

    I am setting up my server still and am testing various plugins - I have Towny right now but I don't like the even blocks it creates for houses.. I don't like building square little buildings.. The only reason, in fact, that I have it at all is to let people have protected plots. Your plugin is a perfect solution for me. That being said, my server is being setup in such a way that players have job roles. What I want to do with protection is have it so specific job roles have the ability to setup lot protection for other players. Is there any way that this plugin could support creating protected lots for other users with a separate permissions node for that? (IE: residence.CreateOther with a /residence CreateO [Username] [ResidenceName]?) The plugin would of course need to look at [Username] to determine max protected lot size and all that, so I'm not sure if that is possible from a permissions plugin standpoint, but I would love to see this.
  18. Offline

    Steve Cole

    I have to agree with Johnathon that this is an Amazing plugin. I would really like group support it would save me from needing to have 2 zone plugins; this one (for enter exit message) and antigrief (for group based permissions.) which ever plugin adds the missing feature first will probably be the one I stick with, kind of hoping for Residence because it is more user friendly would save time with helping new players.
  19. Offline


    i can't create more than one subzone
    i have one main plot and one sub plot but wheni try to make any other plots i get
    "sub zone collides with another sub zone"
  20. Offline


    thanks for ignoring my question.
  21. Offline


    That's from the OP. I think that's what you were looking for, correct? Download the latest version and you should be good to go.
  22. Offline


    I know that denying use for doors was mentioned before. I am using the Lockette plugin which, if used in conjunction with this plugin, works well to prevent players from entering a house (that has move flag enabled) uninvited. If a player is inside the house (with damage disabled) while the owner isn't though, and the door is locked, they will be trapped. It would be nice to just have door use disabled along with chests, instead of having to use a secondary plugin, and, if possible, any player inside the residence the privilege of exiting but not entering, though this would be a problem with any type of jails though.
  23. Offline


    Excellent so far ;)

    are permission nodes in for blacklisting for VIP but not for Default yet?

    I didn't see them under
    Permissions Nodes:

  24. Offline


    You found the VIP node? I don't see it anywhere... Or maybe I am a little slow...
  25. Offline


    Hmm, I still think it would be a little confusing as its another thing you would have to remember when typing commands. I may could still put this in, but It will be a optional feature :)

    Aye, I plan to eventually move over to a MySQL / SQLite system as the current system is not that great, and was just a fast way for me to get saving working. You can expect some form of SQL saving in the future :)

    Hmm, I could probbably do somthing like this. I can just change the /res create command to take either just "name" or both a "name" and "owner" argument. Then it would prompt the user you specify as "owner" if he or she wants to allow other person to create a residence in his or her name. Probbably not too hard to do, will look into it :)

    Thanks :) Also there is group permissions, see the newest version's config file in the groups section. Those groups are mirroring Permissions groups. So if your in the "vip" group in permissions your in the "vip" group for this plugin :)

    It is by design that zones cannot overlap on the same level. This is to prevent another player from coming in and overlaping your zone with his and then locking you out by setting permissions for only him on his zone. I suppose I could make subzones overlap as only the owner can make subzones anyway, but there still could be a conflict of permissions in the place where it overlaps, where only one zones permissions will count and the other will be ignored. This mod really wasn't designed with overlaps in mind.

    Sorry I missed your question, but as Johnathon pointed out, the latest release does address your issue, all protections are now OFF by default.

    As somone earlier pointed out in the thread, theres a bug with bukkit and doors right now, they will get it fixed :) EDIT: Nevermind, its not a bug its more like they are rearranging the code so that doors appear under a different event which hasn't been created yet. Either way, they will get it worked out... :)

    There is no nodes for groups, the groups in the config file mirror the Permissions groups. For example: if your in the "vip" group in Permissions, then you are in the "vip" group in this mod as well, and if your in the "default" group in Permissions then it will use the "default" group for this mod as well. Hope that answers both your questions :)
  26. Offline


    @bekvon - i'll re-clarify my question

    Let's imagine this set up
    I have three groups:
    Default, VIP, Admin
    I want my default users to set regions/cuboid areas so no one can break 'blocks' in that defined area.
    I want my VIP to be able to also set regions/cuboid areas so no one can break blocks - but I also want them to be able to black list players (but not the default group users wont be able to add black lists to their regions)
    I want my admin group to have all of these abilities to stop mob spawning / black list / block protection

    Is it possible to have the permission nodes to residence.blacklist / residence.blockprotection - etc?
  27. Offline

    Steve Cole

    I was thinking more along the lines of creating zones where only vip can build/destroy instead of having to add members individually. I do like the new config file and the different settings per group now tho, means i dont need to use the residence.infinite.* permissions now.

    also don't know if you can or not but I have the worldedit client mod and worldedit installed which shows a grid around its selection, do you think you can tie into that so that the grid shows around a res selection or so res can use the worldedit selection info. just an idea that i got when the grid showed up by accident because res was set to use the woodenaxe too.
  28. Offline


    Here is My Server Log:

    18:10:56 [INFO] Starting minecraft server version Beta 1.3
    18:10:56 [INFO] Loading properties
    18:10:56 [INFO] Starting Minecraft server on
    18:10:56 [WARNING] The server will make no attempt to authenticate usernames. Beware.
    18:10:56 [WARNING] While this makes the game possible to play without internet access, it also opens up the ability for hackers to connect with any username they choose.
    18:10:56 [WARNING] To change this, set "online-mode" to "true" in the server.settings file.
    18:10:56 [INFO] This server is running Craftbukkit version git-Bukkit-0.0.0-544-g6c6c30a-b556jnks (MC: 1.3)
    18:10:56 [INFO] Preparing level "Server_start1"
    18:10:56 [INFO] Preparing start region
    18:10:57 [INFO] [Permissions] version [2.5.3] (Phoenix) was Initialized.
    18:10:57 [INFO] LWC Loading shared objects
    18:10:57 [INFO] LWC Native library: plugins/LWC/lib/native/Linux/i386/
    18:10:57 [INFO] Loaded Essentials build 2.0.298 maintained by Zenexer, ementalo, Aelux, Brettflan, KimKandor, snowleo and ceulemans.
    18:10:58 [INFO] Loaded EssentialsProtect build 2.0.298 maintained by Zenexer, ementalo, Aelux, Brettflan, KimKandor, snowleo and ceulemans.
    18:10:58 [INFO] Loaded EssentialsSpawn build 2.0.298 maintained by Zenexer, ementalo, Aelux, Brettflan, KimKandor, snowleo and ceulemans.
    18:10:58 [INFO] [Permissions] version [2.5.3] (Phoenix) loaded
    18:10:58 [INFO] SimpleWarp version 1.63 is enabled
    18:10:58 [INFO] [AutoSave] Version 1.0.2 is enabled!
    18:10:58 [INFO] [AutoSave] Loading config file
    18:10:58 [INFO] [AutoSave] AutoSaveThread Started: Interval is 300 seconds
    18:10:58 [SEVERE] java.lang.NumberFormatException: For input string: "5;310"
    18:10:58 [SEVERE] at java.lang.NumberFormatException.forInputString(
    18:10:58 [SEVERE] at java.lang.Integer.parseInt(
    18:10:58 [SEVERE] at java.lang.Integer.parseInt(
    18:10:58 [SEVERE] at
    18:10:58 [SEVERE] at
    18:10:58 [SEVERE] at
    18:10:58 [SEVERE] at
    18:10:58 [SEVERE] at org.bukkit.plugin.SimplePluginManager.enablePlugin(
    18:10:58 [SEVERE] at org.bukkit.craftbukkit.CraftServer.loadPlugin(
    18:10:58 [SEVERE] at org.bukkit.craftbukkit.CraftServer.loadPlugins(
    18:10:58 [SEVERE] at net.minecraft.server.MinecraftServer.e(
    18:10:58 [SEVERE] at net.minecraft.server.MinecraftServer.a(
    18:10:58 [SEVERE] at net.minecraft.server.MinecraftServer.d(
    18:10:58 [SEVERE] at
    18:10:58 [SEVERE] at
    18:10:58 [INFO] [AdminMode] Created properties file.
    18:10:58 [INFO] [AdminMode] Permissions 2.5.3 enabled for use.
    18:10:58 [INFO] [AdminMode] Permissions have priority; being an op with BlastPick will do nothing.
    18:10:58 [INFO] [AdminMode] AdminMode Version 0.3 Enabled.
    18:10:58 [INFO] nChat version 0.3 is enabled!
    18:10:58 [INFO] BlastControl version 0.4 is enabled!
    18:11:09 [INFO] LWC Using Nijikokun's permissions plugin for permissions
    18:11:09 [INFO] LWC Loading SQLite
    18:11:10 [INFO] SQLite Using: Pure
    18:11:10 [INFO] LWC At version: v1.63
    18:11:10 [INFO] WorldEdit 4.1 enabled.
    18:11:10 [INFO] WorldEdit: Permissions plugin detected! Using Permissions plugin for permissions.
    18:11:10 [INFO] BedrockControl version 1.1 is enabled with permissions!
    18:11:10 [INFO] [Residence] Found Permissions Plugin!
    18:11:10 [INFO] [Residence] - Save file does not exist.
    18:11:10 [INFO] [Residence] Enabled! Version v1.1.2 BETA by bekvon
    18:11:10 [INFO] [PlugMan] Starting Up! - Version: 1.3 by bekvon
    18:11:10 [INFO] [PlugMan] Found Permissions Plugin!
    18:11:10 [INFO] Done (1.391s)! For help, type "help" or "?"

    Even I have created a residence named Town. when I create a subzone this is possible.. if I want to create a second subzone in Town it says that it's colliding with another subzone...What am I doing wrong???

  29. Offline


    Really nice plugin you made there =). But i have the issue that I can't create subzones. I'm Admin in permissions and get following error if I try to create one: Unknown error occured when creating subzone
    You have any idea what could be wrong?
    And yeah, it is my zone.
  30. Offline


    OK, i think i know what your saying. Basically you want a group permission that allows or disallows players from setting a specific flag for other players on their property. Basically, its a permission that will allow or dissallow the use of the "pset" command. Without the "pset" command, they cannot blacklist / whitelist individual players, they can only set the global +build or -build flag on their residence, but not for individual player. Is this what your getting at? :)

    Oh ok, so you mean group permissions for the residences themselves. Kinda like how with worldguard you can do g:vip to give the "vip" group permission. Yea, this shouldnt be to hard :) I'll implement a "gset" command that will allow you to set flags for groups. EDIT: oh and about the worldedit client mod... depends on if I can figure out how it works or not, but quite possible. Honestly, if you have worldedit installed, and use the same tool as residence, the grid will show up anyway and will represent the same selected area that residence has selected. So, really you don't even need this mod to integrate into the client mod as long as you have worldedit installed.

    Zones cannot overlap in any way. If there is any part of the zone your trying to create that crosses another zone at anypoint, it is a zone collisions and it will prevent you from making it. This is by design, since if two zones overlap and a player walks in that overlap, the plugin wont know which zone the player is in. The exception to this rule is that subzones can of course overlap their parent zone, and they replace the permissions of their parent with their own within their area. Hope that explains it. If you are 100% sure that the zone your trying to make does not collide with another subzone, then it may indeed be a bug in the plugin.

    You, seem to have found a real bug :) I can't quite tell exactly whats broken, but I'm going to go look through the subzone code and see if I can figure out what may have happened. Unknown error, unfortunately, means just that... its unknown, so I may have to dig for a while before I figure it out. Can you tell me a bit more about exactly what you were doing just in case it may help?
  31. Offline


    @bekvon - in a manner of speaking yes. A customizable permission node - The closest plugin I could think of would be WorldEdit.
    You can decide what 'commands' to give for users so if you want them to have fixwater you would do worldedit.fixwater to your VIP group or you can do lava for admins so .. worldedit.fixlava.

    So in your plugin - yes people may have access to the command pset - to set the certain flags - but if they dont have the residence.blacklist permission they wouldnt be able to do blacklisting in that region without it.

    It may be a little confusing but it would consider the pset command its own tree of permissions - so we could break up permission nodes / users even further.
Thread Status:
Not open for further replies.

Share This Page