Bukkit

@ArmyStich

You need to make sure that players have a limit of 0 for the regiongroups they should not be able to buy, check this page for an example of the limitGroups. Did you add your regions to groups inside AreaShop with the '/as groupadd' command?

If you cannot solve the problem with the information on linked page then please give me a description about how you want the limits to work, and then ill provide you some groups.

@Sfmplayer

Ah nice, the lines from the 'flagProfiles' section indeed ensure that the players is added to the WorldGuard region correctly, so removing those is indeed a bad idea as you found out :)

If you have other questions then let me know.

@Sfmplayer

This feature is explained on the Schematics page, if you have any questions then let me know.

@danielfr789

I think your suggestion is already covered by the 'maxRentTime' option in the default.yml file, let me know if that is what you are looking for.

@mathpro

Good that you got it fixed, currently '1 week' is indeed incorrect, weeks are not implemented as a time indicator. I think I will add weeks for the upcoming version, then this kind of problem will not happen again in the future.

@mathpro

Somehow you managed to to get an infinite or incorrect moneyback value for one or more regions. This is breaking the code that renders the number to a formatted string (adding currency prefix+suffix). I have made a change for the upcoming version to prevent this problem.

Things you could check to possibly solve your problem now:

1. The duration of your region should be a proper number.
2. The moneyBack setting in default.yml should be in the 0-100 range (above 100 should not break anything, but would allow players to exploit).
3. Your server time is set correctly.

What also might help to solve the problem is counting how many times this error occurs. You could do this by stopping the server, then starting, then stopping (areashop refreshes regions at startup). Then open the latest.log file and for example search for "NumberFormatException" and see how many hits it has. If it is in the 1-10 range then the problem might be caused by 1 faulty region, if it is a lot more (more as the number of rental regions) then it might be a settings that is applied to all regions.

Let me know if that helps, if you cannot figure out the problem then please create a ticket and give me a link to download the complete '/plugins/AreaShop/' folder.

@ArmyStich

Check the 'inactiveTimeUntilUnrent' and 'inactiveTimeUntilSell' settings in the default.yml file, these should be exactly what you are looking for. Remember you can set all settings that are in default.yml for region groups, and individual regions, so if you need different times for certain regions then that is possible.

@novrom

Currently the money of the rent/buy does not go anywhere, however I have added a 'landlord' implementation to my development version. That should be exactly what you need, if you are familiar with compiling plugins then you could check my GitHub page, otherwise just wait a while until I release an update.

First I want to say something to anyone that commented but did not get answered yet: Thanks for your patience. Normally I'm always trying to answer within 24 hours, but the last 2 weeks I was very busy with my study and therefore have failed to deliver that self-imposed response target. I'm still very interested in AreaShop and am tempted all the time to develop things for AreaShop. But finishing my bachelor degree is simply more important currently. The coming 5 weeks I will still be busy, but after that the holidays start, so I hope to get working on AreaShop a lot at that time.

Now lets get into answering :)

@novelleserver

By default AreaShop already adds the buyer/renter of a region to the 'members' flag of the WorldGuard region. Make sure that the 'flagProfiles' section in your config.yml file is still correct, this is the section that will make it happen. If you want AreaShop to set them as owner instead then check this FAQ item.

@rockindavies21

First check which regions you have at the spot where you have problems with build rights: '/region info'. If you have multiple regions then make sure that the region used in AreaShop has the highest priority, the easiest thing to do is to change the priority of your other regions to -1. If you still have trouble then please give me the following information:

1. AreaShop config files: config.yml, default.yml, groups.yml (if you have that)
2. (screenshot of) Output of '/region info <region>' for all regions at the spot where you have trouble.

@frizzbee30

Thanks for helping while I had no time to reply, and nice that you are using AreaShop with pleasure :) .

@ralphhogaboom

Operators can simply use '/as unrent <region>' and '/as sell <region>' for regions owned by other players. If you want to give players that do not have OP this ability then you can use the permissions provided by AreaShop, check the Commands & Permissions page for those.

@catastrov

Great that you like the plugin :)

1. This feature is already on my TODO list, but there is also a workaround available. You can change the command that is run when a user clicks the sign. So if you change that to a '/tellraw' with a JSON message, then you can make a confirmation thing. You could send a message like this: "Are you sure you want to buy region 'shop-1' for $100? [yes, buy it]", which can be clicked on to execute the '/as buy' command. Then you have a nice confirmation message, which is quite easy to use. I recommend using a site like minecraftjson.com to build the message.
2. If you have bought a region you can actually click the sign to sell it, by default this action is bound to shift+rightclick. If you want that to be rightclick instead then you could change that in the 'signProfiles' section of config.yml. I think keeping the '/as buy' on rightclick even while someone else bought it would be better, since another player would be a message that someone else bought it then, instead of a 'you dont have permission to sell this region'-like message.
3. Currently I'm unable to separate permissions for signs and commands, since the only thing that the signs do is running certain commands like the player would have done them. You might be looking into the wrong solution for the problem though, I think you want the players to be close to the region to buy/rent it? Because then it would be better to solve that problem instead. In default.yml you can already enable that players are required to be in the correct world, or even inside the region to buy/rent it, so that might be useful for you.

PS: biggest post ever ;)