Bukkit

It has taken its time (more as 5 months), but finally the moment is there: AreaShop v2.2.0 is released. I know a lot of people have been waiting for a couple of features in this release (landlords for example), and I have been giving out more dev-builds out as ever before. Check the changelog here.

Because nothing is ever 100% bug-free and feature complete you can make tickets to indicate both of these situations to me, click here. All tickets have been moved to GitHub, where I find they are more easy to manage and organize and all my TODO list entries have been made into tickets.

@felixlechat62

The schematic restore functionality of AreaShop might already work for that, not entirely sure how Quickshop saves its data and handles missing chests and signs though. Please let me know if that works.

Because I expect that an actual integration is necessary I made a feature request ticket. To confirm, is this plugin the one you are using? (there is another which looks outdated).

@EnderdragonDotDe

That might indeed do the trick, will think about that when implementing something to prevent the inactive time kicking in.

@jobronies

You can use the 'eventCommandProfiles' section to do this. In the 'after' node of 'rented' you could place a command to teleport the player to the cell ('sudo %player% as tp %region%'), and then a command to set their home ('sudo %player% sethome home'). The 'sudo' part is a command from Essentials, this is required because the commands are ran from console.

Instead of setting their home you might also simply promote the '/as tp <region>' command, by default players will already be able to use this for their regions (and any friends they add can also teleport to the region). This can be changed by permissions.

@ArmyStich

First of all it is good to read the information on this page, and checkout the example.

One thing to note is that region group names have nothing at all to do with limit group names. The way you link them is by specifying the region groups in a 'groups:' section inside the limit group (see the example page).

A second thing is that you will need an blocking limit group for each rank you want. This group has the same selectors as the normal one (worlds and groups thing), but has limits of 0 as total, rents and buys. You can assign these blocking groups to everyone by applying them to the 'default rank', and then give the appropriate rank the non-blocking groups.

If you need help with a specific setup then let me know. I will try to add a typical prison-like setup example to the examples page soon.

@XXLuigiMario

Make sure that when using '/as info region <region>' or left-clicking the sign it indicates that the region will restore at unrent/sell. That is the way to check if a region is correctly setup for saving/restoring. Make sure you have restoring enabled in the config.yml file AND default.yml file. Yes this is confusing, the config.yml settings is already removed for the next release.

Making a schematic with McEdit or WorldEdit should not be required, AreaShop should correctly save it when renting a region with your config.yml setup. If you still have trouble after checking the above tips then please let me know.

@funkay91

I'm actually trying to work towards a release, already moved all tickets to Github and organised the work that is left. I'm planning on resolving the tickets marked with the 'v2.2.0' milestone, and then releasing it (only 1 ticket left). All feature request made by people, or ideas by myself are also on the Github issues page now.

The last week I already did some coding to implement last things and fix things, as you can see in the commit history. I have even written most of the changelog already, so it should get close now, still cannot give you an exact date though since I'm busy with my new job.

@EnderdragonDotDe

That would only solve the problem partially, because often you would want to cancel the inactive timer when someone is already offline, and possibly close to the set limit. So then this method would fail. You solution would however fix things like no timeout for VIPs. So I might consider still implementing this feature.

@IlPoeta05

The thing with chest access is incorrect in the video, check this FAQ entry for the correct flags. I have asked the video author for an annotation to fix this, but I think he forgot about it.

What you are trying to get done with the rental times is not currently possible (without doing weird stuff with eventcommandprofiles), and I think there is a better way to solve it. You could simply set the rental time to less than 3 days (1 day for example), then set 'maxRentTime' to 3 days, and keep maxExtends at -1. This would make sure that the player would never be able to have the region rented longer as 3 days, and that when the region is at 2 days or less that he could extend it by 1 extra day. So that should be the solution for your situation (make sure you understand maxExtends and maxRentTime, those are different things and you might be understanding the first one incorrectly).

@chikken001

The plan is to work toward this functionality, but I can already say you that it might take a while. This is because these kind of things are complicated, and you as a server owner should be able to limit this in a lot of ways (max created regions, places they can be created, max size, etc). For the upcoming version I already implemented the first steps for this kind of functionality, namely that you can assign a landlord to a region. This landlord will get all profit, and can set the price, duration, teleport location, etc.

@EnderdragonDotDe

I don't exactly get your suggestion, do you want to be able to set a permission for a region and then only when a player has that specific permission they can buy/rent the region? I specifically don't get what you mean with the 'save it in the <regionl>.yml file'-part.

@TNTUP

I don't know about any bugs with '/as addfriend', it is hard to say anything useful about it when I have this little information. If you have a clear case where a friend got removed then let me know.

Your config looks fine, nothing out of the ordinary.

@HypnoticParadox

Setting up a region to use with AreaShop is explained on this page, remember that AreaShop is for selling/renting regions and has nothing to do with items. If you want players to be able to use the regions as item shops, then you need to use something like the trade signs of Essentials or the ChestShop plugin.

@c0wg0d

To get the username of the renting/buying player you can use %player% (all variables described here can be used), a variable for date/time is not there yet indeed. I added that to my TODO list. If you have rental regions then you could use the %until% or %untilshort% tags for now, those give the date that the rent runs out (long or short version), which are save to consider unique.

@PowerHustlers

The limit system is explained in more detail on this page. If you have any questions after seeing the example on that page then just send me a message.

@JackCross14

Please send me the log file of your server (the 'latest.log' file inside the logs folder), that should indicate what is going wrong (probably one of the dependencies is incorrect).

@EnderdragonDotDe

I initially wanted to add a bypass permissions, but that does not work since I cannot get permissions from an offline player.

As you know you can set the mentioned setting in default.yml, this also means you can use this setting in groups and individual regions. If you make a group which has this setting set to -1, then you can simply assign this group to any regions that you want to turn off this inactiveSell feature. Let me know if you need help setting this up. So a blacklist would not add much to the existing system.