Bukkit

@Camaroz1

After adding regions to a group you can set certain options for all regions in the group (price, duration, sign layout, restoring on/off, etc.). If you for example want the sign for 20 regions to look different or show other information then you can add all these to a group and then set the signProfile setting to something different for this group. All the settings in the default.yml file can also be changed for groups and individual regions (check the Config page for where to put the settings). For all the settings that use profiles you need to change/add a profile in the config.yml file (explained above the section in the config.yml file).

How the inheritance system works can also be found on the Config page, basically it is like this: individual settings > group settings > default.yml settings (ones earlier in the list override later ones). Next to that you can also add multiple groups to a single region, if you want to change the signs of 20 regions, but want to change the restore setting for 10 regions from this set, then you can use that for example.

In the upcoming version groups can also be used to limit renting/buying the number of regions a player can buy in a group (upcoming features on this page, third bullet point from the bottom).

The documentation inside the default.yml and config.yml file has already been improved for the next version that will be released and will hopefully be a bit easier to understand.

@TheL0w3R

I'm sorry but I will not do a major rewrite to support/switch to SQL just because a couple of players like editing SQL databases better then flatfile. The current YAML format is for most people easy to edit, and very accessible. If the plugin would use SQL however it would be very hard to access, because I'm sure most users of the plugin don't really know how to use PHPMyAdmin and also don't know the SQL syntax to make changes. Only if I know switching to SQL will have a couple of significant advantages then I will consider it. And the SQL syntax is no problem by the way, did a course about that at the university. I know the basics about how to implement it in Java, but for implementing it nicely (easy to maintain, easy to read) into the plugin I have to think about it for a while.

@DarkCrimsonFury

It looks like you are using AreaShop v2.0.2 with WorldGuard 5, you need to have WorldGuard 6 for this version. If you want to keep WorldGuard 5 you need to downgrade AreaShop to version 2.0.1. Thanks for helping Androkai, but this time you are not correct, the version of Bukkit is not the problem this time, 1.7.9 is supported by these versions of AreaShop.

@AttaWishes

You can still get it to work, you can simply change the AreaShop config to add the player that rents the region as owner of the WorldGuard region instead of member. Then you can give owners of regions the permission to add members and then it will work as expected. Open your config.yml file, then scroll to the 'flagProfiles' section, and then change the line 'members: +%player%' in the 'rented' and 'sold' section to this line: 'owners: +%player%'. Then it will add the player that bought/rented the region as owner and then it should all work.

@AttaWishes

That feature will be added soon I think, but until then you can use the workaround described in comment #214, also make sure you follow the link to comment #204 from there, that is also an important part of the workaround.

You say 'Sell regions ruins the game ...', if you are referring to the '/as sell' command: You can simply deny the permission to this command and then players cannot sell their regions anymore (check the Permissions page). If you are referring to the buy/sell region in general: Then just create rental regions and then the players need to pay for the duration each time.

And WoldGuard 6 is already released (it is beta, but still). If you are using WorldGuard 6 you need to have AreaShop v2.0.2 installed, and if you are using a older WorldGuard then you need to have AreaShop v2.0.1 or older installed.

@KleinesGumi

It looks like you are using AreaShop v2.0.2 in combination with WorldGuard 5, this does not work. You need to downgrade AreaShop to v2.0.1 or lower or upgrade WorldGuard to version 6 (check their page). If you still have a problem let me know.

@TheL0w3R

MySQL support is not something I can add in a day, that would require a major rewrite. I do however know the SQL syntax and I think I'm able to use it in combination with Java. I'm probably not going to support SQL anytime soon, just because it is a lot of work and I don't want to do that if it is not going to improve performance of the plugin greatly.

What is exactly the reason you want support for it? Because I think the performance of the plugin is not bad at all at the moment. The only problems that the last released version has is that it does certain updates for all regions in just 1 tick. For example the command '/as updaterents' will easily lag the server for a couple of seconds or even longer if you have a lot of regions. But this example has already been fixed for the next version, now commands like this update a certain number of regions per tick, spreading the load and preventing a lag spike for your server. This periodic updating already applies for the following: The '/as updatebuys' and '/as updaterents' commands, checking for expiration of rent regions, checking for regions of inactive players (auto-unrent/buy), periodic updating of signs for things like timeLeft tags.

If you have any other performance concerns, just let me know and I will try to fix them.

@Guble

Normally the sign will appear at the previous location I think, because if you don't hide the sign it will just still be there. I could add permissions to let players connect more signs to their regions, then they could place a sign at the location they want. And also a way to delete signs for a region of their own, then the players can fully decide where the sign(s) will be if they have certain permissions.

@donutnut1

Normally a WorldGuard region only allows members and owners to break blocks, open chests and use other things. So be sure you have the WorldGuard region set up correctly, because basically the only thing AreaShop does is adding the renter as a member of the region. You can also let AreaShop automatically set certain flags for specific states (forrent, rented, etc) of regions, you can check the Config System page for all options.

As @Androkai said, you probably have the 'use' flag of the WorldGuard region set to 'allow', this will allow all players to use chests, furnaces and other inventories. If you just reset this flag (set it to 'none') it will only let the members and owners use these inventories again.

@Guble

Okey now I understand what you want to do. I think the easiest solution would be to set the 'sold' signs to nothing, then they will get deleted when the region is sold (already in the plugin). Then all the other things work like normal (player is owner, region stays registered in AreaShop). And if the player wants to sell the region they can use a command like '/as setforsale <price> [region]' (to be added in the plugin), which will show the normal 'forsale' sign again. And doing this does not bulldoze the region, the owner stays owner until a player buys it and the money will go to the previous owner of the region when it is sold. If you use something like this you probably also want to prevent selling regions back the previous owner or server with '/as sell', that can already be done by denying the permission to use this command.

This way the players don't have to place any signs and don't have to be educated what goes onto the signs, so I think this would be the most user friendly solution. Would this solution fit your needs?

Maybe we could allow a player that bought a region to also set his region up for rent to other players, but that is something you don't want to use for now as I understand (will have separate permissions anyway).

Something like this won't be added to rent regions I think, because you are not the actual owner and therefore cannot sell/rent the region to another player.