Upstream/AreaShop
1
0
Fork 0
mirror of https://github.com/NLthijs48/AreaShop.git synced 2024-11-29 05:35:12 +01:00
Code Issues Projects Releases Wiki Activity

Created Frequently Asked Questions (markdown)

Thijs Wiefferink 2015-08-24 18:20:44 +02:00
parent 19ffa47a1d
commit 7e3b0ed0dc
1 changed files with 75 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

75
Frequently-Asked-Questions.md Normal file

@ -0,0 +1,75 @@
#### How to disable the greeting messages that AreaShop regions have?
If you don't want the greetings then you can disable them like this:
* Open the config.yml file that is inside the AreaShop folder
* Scroll to the `flagProfiles` section
* Change each line that starts with `greeting:` to this:
`greeting: ''`
* Save the file, then use `/as reload` or restart your server. All regions should be updated by `/as reload` if you use AreaShop V2.1.5+.
#### Why can't the buyer/renter of the region build inside of it?
You probably have more regions at the same spot as the region you use for AreaShop, this prevents the members/owners of the region from building inside of it. You can set the priority of other regions to something lower than 0 with `/region setpriority <region> <number>`, if that is not an option you can set the priority of the AreaShop regions to something higher:
* Open the config.yml file
* Scroll to the `flagProfiles` section
* Add the following line to all the sections that are inside the `default` profile (be sure to indent this line with the same number of spaces as for example the `members` one):
`priority: 1`
* Save the file, then use `/as reload` or restart your server. All regions should be updated by `/as reload` if you use AreaShop V2.1.5+.
#### How can I set the buyer/renter as owner of a region instead of member?
*Quick answer:* Replace `members:` in the `flagProfiles` section of the config.yml file to `owners:` and then use `/as reload`.
You can completely customize which WorldGuard flags AreaShop should set for regions, including how it should add the renter/buyer, and friends. The `flagProfiles` section in the config.yml file contains all options for WorldGuard flags. Currently there are 5 states a region can be in (forrent, rented, forsale, sold, resale), for each of these you can set the flags that you want.
\\Things that might help you:
* You can set the priority of a region here just like you would set a flag, this helps if you have other regions interfering (add the line to all states).
* You can set group flags to for example only give access to chests for the renter of the region: `chest-access: 'deny g:non_members'`
* You can use all variables in these flags as defined in the config.
* The `owners` and `members` flag take UUIDs as arguments, but also accept names (`n:<name>`), and permission groups (`g:<group>`).
* Use `''` as value of a flag to reset it.
#### How to setup different limits for different players groups and worlds? (how many regions each player can buy)
First of all read the text above the `limitGroups` config section inside the `config.yml` file, that is the basic information you need. An advanced example about most aspects of the limitGroups section can be found here: [advanced limitgroups setup examples](http://dev.bukkit.org/bukkit-plugins/regionbuyandrent/pages/advanced-limit-groups-setup-example/).
#### What happens when a player changes his name?
**General notes:**
* If you have your server in offline mode (and are not using the `bungeecord: true` setting for when you have a BungeeCord network) then a player will lose his bought regions anyway because the UUID's returned by Bukkit/Spigot will change anyway.
* Even when the sign and/or greeting is showing an old name, the correct player will still be paying for the region. That is because AreaShop uses UUID's and that ensures the correct player is accounted for, the old names on signs/greetings is simply because those did not get updated yet (starting from AreaShop V2.1.5 they automatically update).
**Using AreaShop V2.1.5 or higher:**
* Name changes are fully supported and should give no trouble at all. When a player with a changed name logs in AreaShop will detect a name change and then updates all of his regions. That ensures that even when you use WorldGuard 5.X the player will immediately have access to his region again and also ensures that the signs and greeting messages show the new name of the player.
**Using an older AreaShop version:**
* Update if you can, that is simply the best idea to handle it best (be sure to backup your server before upgrading as always).
* Since AreaShop V1.3.0 the players that bought/rented a region are saved with their UUID instead of their name, so from this version a user would be registered correctly in the system of AreaShop even after changing his name.
* If you use AreaShop V2.1.0 or higher in combination with WorldGuard 6.0 or higher then the user should be able to use his regions as normal directly after his name change (after re-logging with the new name of course), but the old name is still displayed on the signs and in the greeting message (manually update with `/as updaterents` and `/as updatebuys`, or simply update to the latest AreaShop to automate it)
* If you use a version of AreaShop between V1.3.0 and V2.1.0 or WorldGuard 5.9, then the AreaShop region of the player that changed his name will need to be updated first before he can use it again. You can do this by using `/as updaterents` and/or `/as updatebuys`. (WorldGuard 5.9 uses names as members/owners of regions, so AreaShop could not properly add a player, but could only update it after a player changed his name)
#### How to prevent players from opening chests in regions that other players bought/rented?
To prevent other players from opening and using chests in regions that are bought/rented you can add a line to the `flagProfiles` section in the config.yml file. The `flagProfiles` section describes which flags AreaShop should add to the WorldGuard region and which value they should have. To disable using chests you can add the following line: chest-access: `deny g:non_members`, that would disallow using chest for anyone that is not a member or owner of the region. The complete `flagProfiles` section in the config could look something like this after you added it:
```yaml
flagProfiles:
default:
forrent:
members: ''
greeting: '%lang:prefix%%lang:greeting-forrent%'
chest-access: 'deny g:non_members'
rented:
members: '%uuid%, %friendsuuid%'
greeting: '%lang:prefix%%lang:greeting-rented%'
chest-access: 'deny g:non_members'
forsale:
members: ''
greeting: '%lang:prefix%%lang:greeting-forsale%'
chest-access: 'deny g:non_members'
sold:
members: '%uuid%, %friendsuuid%'
greeting: '%lang:prefix%%lang:greeting-bought%'
chest-access: 'deny g:non_members'
resale:
members: '%uuid%, %friendsuuid%'
greeting: '%lang:prefix%%lang:greeting-resale%'
chest-access: 'deny g:non_members'
```
The above assumes that you also want players unable to interact with chests if the region is not rented or bought. If you however want to allow raiding of abandoned regions you can change the chest-access lines of the `forrent` and `forsale` sections to the following: `chest-access: 'allow'`, which allows anyone to use the chests.
#### How can I use items as currency to pay for regions of AreaShop?
AreaShop supports all economy plugins that are supported by [Vault](http://dev.bukkit.org/bukkit-plugins/vault/), so if you want to use items as currency then you need an economy plugin that has that and also works with Vault. The [Gringotts economy](http://dev.bukkit.org/bukkit-plugins/gringotts/) should work for this purpose, this plugin has been successfully used by a couple AreaShop users. There might be other suitable plugins to do the same thing though.