Bukkit

I think I made quite an interesting commit to the repository of AreaShop, the reselling feature has been added! So that is out of the way and now the release is getting closer. Something I recently changed: I'm committing and pushing to the repository every time now, instead of only at updates I release here.

I'm also trying to get some more translators so that AreaShop can have more fully updated languages included into it. Do you want to help? Go to this page and read the section below the 'Option #2' header. Translating goes through the Transifex website and is very easy, sending files back and forth is not needed, you can translate lines online and whenever you want. Every line you translate will be saved, no need to do it all at once (this also allows for easy collaboration).

@tk11

To introduce an extra step for selling/unrenting a region you could change the command that will get executed when you click the sign. If you change it to just a tell message to the user "Use '/as unrent %region%' to confirm that you want to unrent this region" Then the user cannot accidentally unrent the region anymore. You could improve this by sending a message with the '/tellraw' command that contains a word you can click to unrent the region. So then the flow becomes like this:

1. User shift-rightclicks a signs
2. User sees a message in chat: "Click here to confirm that you want to stop renting %region%, this will bulldoze everything in the region" ('here' contains a click effect that executes '/as unrent %region%', use a site like this to get the tellraw text).
3. User clicks the 'here' text
4. The '/as unrent %region%' command will be executed, the region will be unrented and possibly restored from a schematic

Complete tellraw command following the example above: /tellraw %player% {"text":"","extra":[{"text":"Click "},{"text":"here","bold":"true","clickEvent":{"action":"run_command","value":"/areashop unrent %region%"},"hoverEvent":{"action":"show_text","value":{"text":"","extra":[{"text":"Click to unrent %region%","color":"white"}]}}},{"text":" to confirm that you want to stop renting %region%"}]}

One flaw with this example is that the current renter of the region will always receive the tellraw message, and not the player that actually clicked the sign (there is no variable for that currently).

Hopefully that helps you to get something you want, if you need any more help with it just send me a message.

@Ironic8b49

After you changed the timeformat settings in the config you need to update all signs to let them show the new format. This happens when the state of the region changes (somebody rents it for example) or when you use the '/as updaterents' command. So if you use that command then all signs will be updated and should show the new timeformat.

@Onewingseraphim

I indeed tagged the wrong guy, fixed it now :)

@luckybowers

By default it should be exactly like that, normally regions do only allow players that are member or owner of the region to build there. And AreaShop normally adds the player that bought/rented the region to the members list. First you should check with '/region info <name>' on the shop region to see if the 'build' flag has been set (it should not be). As second you want to check if you have any other regions at the same spot as the shop region (rightclick with leather on a block in the shop). If you for example have a big region around all shops then you need to make sure the shops have a higher priority then the big region (use '/region setpriority <region> <number>' or add a 'priority: 1' line to the 'forrent', 'rented', 'forsale' and 'sold' sections of the 'flagProfiles' section in the config of AreaShop, then it will automatically set the priority to 1 when somebody rents/buys a region. or you could use '/as updaterents' and '/as updatebuys' to update the regions).

Let me know if you solved the problem, otherwise you could maybe send the ip of your server to me in a PM and then I could help you that way.

@Onewingseraphim

:D

@luckybowers

Are you sure you added those WorldGuard regions to AreaShop? Did you follow the instructions on the 'Setting up regions & signs' page? If you execute the command '/as info all', does it list any regions?

@Onewingseraphim

Yes, you can make use of the 'eventCommandProfiles' section of the config. Here you can add a command to the 'before' section inside the 'unrented' section. You could use a command like 'tp %player% 0 128 0' to teleport the previous owner of the region to spawn (change to coordinates to your actual spawn). Or if you don't have a delay on the '/spawn' command then you could use the line 'spawn %player%' to teleport them to spawn (the /spawn command is from Essentials).

If you have any other questions just leave a message.

@Ironic8b49

The changelog that comes with v2.0.2 describes the changes in comparison to v2.0.1, the only important thing is the switch to WorldGuard 6. So for now you can just stick with v2.0.1 if you want, but for future update you will need WorldGuard 6 anyway so if you want to keep it up-to-date then you need to update it sometime.

@Ironic8b49

Yes you can let players place Essentials sign within the shop, that is exactly how I use the plugin myself. Be sure you enable saving/restoring from schematics, because otherwise these signs will stay after the rent of the region runs out (or got sold) and then the next owner will not be able to destroy the signs because they belong to another player (Essentials will only let the player that made the sign remove it). Check the Schematics page to see which config values you have to change to enable the restore functionality.

If you have any other questions just leave another comment.

@Hangjai

The plugin will automatically read the 'rents' file and convert it to the new format, nothing special you have to do with that. You should however make a backup of your worlds before updating. The changelog of v2.0.1 specifies this information, and also lists the changes.

Basically the old 'rents', 'buys' a config.yml will be moved to the #old folder as backup and then new config.yml and default.yml files will appear plus a 'regions' folder that contains one file per registered region. After you upgraded be sure to check the config.yml and default.yml files and set the options as you like.

If you have any trouble with upgrading just ask.