Updated Frequently Asked Questions (markdown)

Thijs Wiefferink 2017-01-29 00:35:02 +01:00
parent 63b79824f5
commit 5dd82e5045

@ -24,13 +24,8 @@ If you don't want the greetings then you can disable them like this:
1. Save the file, then use `/as reload` or restart your server. 1. Save the file, then use `/as reload` or restart your server.
#### Why can't the buyer/renter of the region build inside of it? #### 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: 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.
You should also remove the `block-break`, `block-place` and `build` flags from the `__global__` region (set `passthrough` to `deny` instead) and also remove them from big surrounding regions (the flags are useless there, regions are protected from block break/place by default!).
1. Open the config.yml file
1. Scroll to the `flagProfiles` section
1. 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`
1. Save the file, then use `/as reload` or restart your server.
#### How can I set the buyer/renter as owner of a region instead of member? #### 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`. *Quick answer:* Replace `members:` in the `flagProfiles` section of the config.yml file to `owners:` and then use `/as reload`.