Upstream/AreaShop
1
0
Fork 0
mirror of https://github.com/NLthijs48/AreaShop.git synced 2024-11-25 19:56:26 +01:00
Code Issues Projects Releases Wiki Activity

Improve information about block placement issues

Thijs Wiefferink 2018-02-22 14:55:31 +01:00
parent 2af93a6512
commit 6c80ed3418
1 changed files with 19 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
Frequently-Asked-Questions.md

@ -25,8 +25,25 @@ 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. There are a couple common problems that cause this, try these things:
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!).
**When the players gets a message from WorldGuard like "Hey! Sorry, but you can't place that block here.":**
- Make sure there is no `build`, `block-break` and `block-place` flags on the `__global__` region. Remove those flags with `/rg flag __global__ <flag>` and instead set `passthrough` to `deny` with `/rg flag __global__ passthrough deny`. This change will make everything protected by default, while still allowing other regions to override protections.
- Make sure that all other regions that are at the same spot of the AreaShop region have no `build`, `block-break` and `block-place` flags. Regions are protected by default, so these flags are not required and will cause issues.
- Make sure that the AreaShop region has the highest priority (AreaShop sets it to 10 by default).
- Make sure `/as info region <region>` indicates that the region has been bought/rented, if it does not: rent/buy the region.
- Make sure `/rg info <region>` shows at least one owner/member, if it does not: reset your `flagProfile` section in the `default.yml` file to the one listed in the [standard config](https://github.com/NLthijs48/AreaShop/blob/master/AreaShop/src/main/resources/default.yml).
- Make sure the walls/floor/ceiling of your region are not made of concrete. There is a bug in WorldGuard that prevents placing blocks against concrete, even it players are supposed to be able to do that.
**No message at all:**
- Check that `spawn-protection` is set to `0` in the `server.properties` file, otherwise non-OP players cannot build in a certain area around spawn.
**Another message:**
- Most likely another plugin is blocking block placement, you might be able to find out which one if you follow these steps:
1. Look at a block in the AreaShop region.
2. Use `/wg debug testplace <player>`, use the name of the player you are testing with.
3. It will show in chat if the block placement has been blocked, and by which plugin.
- The same as above works for breaking blocks, use `testbreak` instead of `testplace`, and make sure you are looking at a block inside the region, not at the wall/floor/ceiling.
### 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`.