Inactive [SEC/MECH/ECON] Residence v2.4.2 - Self serve area protection system! Buy/Sell Land! Economy! [1185]

MOVED TO DEV BUKKIT:​

http://dev.bukkit.org/server-mods/residence/​

​

​

​

​

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​

Wiki: Residence Mod Wiki​

Developer API: Wiki​

GitHub Source: GitHub​

DevBukkit Project Page: DevBukkit​

​

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) Features (close)

• 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) ChangeLog (close)

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
  

 

Hmm, I just realized that group names are stored internally as their lowercase versions, but when you go to set flags, it doesn't force the group name to lowercase... I'm going to go ahead and force group name input to lowercase to prevent problems with that in the future. Based on the command you said you used, it looks like you weren't using uppercase, so I'm assuming that this actually isn't the problem you were having... I'll go play with it and see if I can figure it out As for your question... something like that is possible, but it could get really complicated really quickly... I'll think it over and see if theres a easy way to do it

Hmm, yea that's a possibility quite a neat idea actually. Im working on item blacklists / whitelists right now though, so will probably be a little while before I can do that.

 

Using subzones in version 2.0, any subzone deeper than the first one cannot be created, because it collides with another.

Also, standing in a subzone and typing /res info gives information for the zone instead of the subzone, like I would expect.

 

bekvon, onPlayerQuit --> PlayerQuitEvent

 

I'd also like to add that sub zones don't show in the /res list for your owned residences. In my server, we protected our main city and then made each player's home/building a subzone that they own. For all of them, their list is empty.

 

Found the bug, it wasn't that you couldn't add subzones, it was just that it was improperly detecting the name of the zone you were inside. So if you did /res subzone with the full name, it would work. It was the same issue with /res info too, so both should be fixed now thanks for pointing it out.

Its been done, don't know why it still complains

Yea, I been meaning to add that for a long time... I'll get to it

 

All my users can make selections if they have the item specified in selectionItemId. Is there a way to stop this? Only the Admin group and one individual has any permissions for this.

 

Well, even if they can select, they shouldn't be able to do anything with the selection if they don't have permissions for anything. But I guess I could add a check in there just to stop the messages.

 

Hmm, well i was usuing lowercase. I was type /res gset default build true. I probably needed to do /res gset Default build true as my default account has a capital D. It was probably allowing default to build and not Default. Why didn't i think to try that haha.

Thanks again, i'm going away today. Well, now actually lol need to leave. I'll be back Tuesday and i'll get more of the wiki done that week. I'll try and get a finished and up to date copy of everything.
-DanJames

Also, i know i'm just firing requests at you lol. If you don't like them or dont think they would be useful to anyone but me then don't add them
But what about an option to assign residence to a list, instead of linking with a player.

An example of this would be in my town i have 6 outlines on the floor where players can buy land. Every shop, building etc in town is a residence so i can lock them if needed. The farming patches are buyable residence.

It might be useful to assign these to a list called town, instead of them showing up in my /res list.

Then you could have all shops in a list, all houses etc. Maybe you could assign default falgs to a list, and then whenever you add a residence to that list, they get the default flags of the list, instead of the main default flags.

Something like /res create <residence name> [list name: optional] if a list isn't defined, it's linked the the account making the residence.

This might be useful to people like me who have LOTS of world residence, but don't want them showing up is /res list.

But like i said, this might only be useful to me and if it is then there is no point adding it
-DanJames

 

I'm just wondering if it still actually creates the selection (but not the residence of course) and if that wastes any memory, cpu cycles, bandwidth when everyone is gardening with the tool I chose haha.

 

@bekvon Just tried the latest version as of this post and got:

[SEVERE] No enum const class org.bukkit.Material. loading Residence vv2.0 ALPHA (Is it up to date?)
java.lang.IllegalArgumentException: No enum const class org.bukkit.Material.
at java.lang.Enum.valueOf(Enum.java:214)
at org.bukkit.Material.valueOf(Material.java:14)
at com.bekvon.bukkit.residence.itemlist.ItemList.readList(ItemList.java:118)
at com.bekvon.bukkit.residence.itemlist.ItemManager.readLists(ItemManager.java:40)
at com.bekvon.bukkit.residence.itemlist.ItemManager.<init>(ItemManager.java:23)
at com.bekvon.bukkit.residence.Residence.onEnable(Residence.java:116)
at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:127)
at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:578)
at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:216)
at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:115)
at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:93)
at net.minecraft.server.MinecraftServer.e(MinecraftServer.java:215)
at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:202)
at net.minecraft.server.MinecraftServer.d(MinecraftServer.java:142)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:257)
at net.minecraft.server.ThreadServerApplication.run(SourceFile:375)

 

Have you tried latest snapshot? Those are fully updated and working just fine for me.

@bekvon
Found something else; if you as an admin set flags like -move and you transfer ownership to someone else
those flags are reset to default, is this intended?

EDIT:
And I get reports now that, even though the player has +use in 'other flags', they can't use in there residence even though they are owner. If I put the global flag for the residence on +use the player can use it.

 

Is there any chance to save the old residences?
I created over 100 residences for my server and if they are away, it would be very bad

 

Next week I will look at adding a system to convert 1.2.8 saves to 2.0 saves. No promises though.

 

Oh thanks <3 That will be perfect!

 

Heya, just wanted to say keep up the good work. My community loves this mod.

 

@Tjezee yes at the time i was using the latest snapshots

 

so just to make sure. will we have to wait for the next updated to come out for the "you dont have premission to use t his" message to go away?

 

Hi ppl.

Got a problem with the flags... (see scrennshot attached).

First of all... everyone without "residence.admin" got the message "you don't have the permission to use this" on every action. Deleting Craftbook "fixed" this.

But now residence don't accept the Owner flags. It just uses the public flags.... dunno why... someone else got this? Or know what i did wrong?

Regards, Timber

 

@Timberman
Thats what I said couple posts up

 

hmm... tired of reading... But k than i'll give all admin until this is fixed... (if its a bug)... spent a couple of hours and getting rid of this xD

But anyway... if it works correctly.... it's one of my absolute favority plugs

 

Something that has started to occur since your last changes. I have a residence, our main city, set up. I created a subzone and sold it to another player for their lot of land. Their zone has -use, and it shows them having +use. They can't seem to use. Build seems to work fine. Also, setting container to false for the zone, but true for them doesn't work.

WestCoast -> Main zone: +use, -build, -creeper, -tnt
WestCoast.Estate -> Her subzone: -use, -build, -creeper, -monster, -container

Username: Sverna, permissions +use, +build, +move, +container

Not sure if I'm doing something wrong or this is a new bug. Considering the other zones set up in this fashion previously worked right.

Also, I noticed that in a previous update you made usernames lowercase, and now they are case sensitive. Had to redo a bunch of user permission as I had put in 'maxhamer' for 'Maxhamer'. I'd prefer all things handled case insensitively, since you can't really have two minecraft accounts with the same letters, different case.

 

I'm sure this is one of bekvon's aims. He mentioned it above.
-DanJames

 

I'm getting reports that people have lost the ability to use thing, even though they own the zone and their flag is +use

 

This is related to the half built item blacklisting system thats in the shapshot. It can be safely ignored for now until I finish it I'll goahead and see about trying to stop the message from hitting the console though.

Hehe, there may be a small hit to performance, but selection is relativly lightweight when it comes to cpu. The more heavy stuff is done at residence creation, which is good since that happens much less often

That would be awesome if you could do that I've been dreading having to go back and try to hack somthing together to convert the formats.

Looks like I used the wrong function in doing +use and +container checks when I redid the use flag, it was only checking global flags. Should be fixed now, give it a try.

Also about the case sensitivity, unfortunatly as iConomy's bank accounts are case sensitive, we had to move over to case sensitive names. Its looking like iConomy may eventually be replaced with MineConomy anyway, and if that happens perhaps we can return to case insensitive, provided that MineConomy is case insensitive.

Try the latest snapshot if your using 2.0. Otherwise, wait for 2.0 to be done, as save files aren't yet compatible.

 

100% Now it works fine =) GJ!

 

Completely understandable, just wasn't aware of the change. Though, until MineConomy's adoption reaches a point far enough that I can switch, (Such as localshops adopting it, or a fork.) I would hope that you'd retain iConomy support until such a time.

Might I recommend having, in your post, a spoiler tagged changelog for the development of 2.0. Following commits is fine for most people, such as myself, but not always straight forward. (I know, in the past in projects I have committed three unrelated changes in one commit and only mentioned one in the description, leaving people scratching their heads.)

 

Hi there,

if Residence ist enabled, no monsters spawn on the entire map... anyone else got this?

Regards, Timber

 

Need a option to enable and disable selection, it interferers with WorldEdit and so i had to change select tool to slime ball. and/or add permission node to allow/disallow selection. Would be nice.

 

Great plugin, thanks a lot! I am still using 1.2.8 on 617 btw, and it's working great! No bugs so far.

A question: What does the "flow" flag do?

A few suggestions:

• Allow global flags to be set per world (so I can enable pvp/fire/explosions in the nether, but disable them in the main world)
• Allow TNT and creeper/ghast explosions to be toggled separately (like WorldGuard)
• Allow fire spread and lighter usage to be toggled separately (like WorldGuard) since currently, it prevents people from using the lighter at all. This means they can't make fireplaces or activate nether portals. Also, an option to disable fire from lava would be nice too.
• Shorten the flag commands from /res set <flag> <true/false> to /res +/-<flag> as suggested earlier.
• Allow easier adding of players to a res with /res allow <player> instead of /res pset <player> build true and /res pset <player> use true.

Thanks!

 

How can i make people make residence without moneyy? because i only want to protect areas