WORLDGUARD-3152 - Reported by TNTUP

Summary of issues I found: (NOTE those issues are being tested on a TEST server)

1. BUILD flag overrides everything, no access (players) (Build allow in player's regions), no luck
2. Priority (higher numbers) doesn't work, usually created regions on global already overrides BUILD flag
3. BUILD deny flag invincibles players (mobs, falling, pvp) but in protected regions, and allowed regions. In global without BUILD flag the falling, hit by mobs, pvp is fine
4. Allow door interacting only (?)

OK:

BUILD flag or not allowed (without BUILD flag) cannot interact with doors/entities/chests

1. My server's global has the BUILD deny to prevent illegal building (mostly blocking for mining, I have a mining world!), theres players's own regions, they cannot build/interact/pvp/entity hit/no falling because of the global's BUILD deny. The region global isn't supposed to override player's regions because it has no priority, but player's regions do, they'Re set at 0, I tried setting a higher number, no luck.

2. I tried higher priorities depite BUILD deny set to global in player's regions, no work. Player's regions priorities, some are set to -1 because they manage their own town/city that theres sub-regions that their pritority is at 0. Player's regions (personal use) priorities are set to 0.

3. The BUILD deny flag also invincibles players to be killed by monsters, falling, pvping etc. Without BUILD deny, everything is fine, but in non allowed regions (theres no BUILD deny!) same issue if BUILD deny were added in that player's region.

4. Doors are automatically blocked by interacting them, couldn't allow those only like as before? (Using LWC for this)

Warning: My english is poor so sorry if I did misspelling or bad grammar. If other issues discovered, ill create another ticket or reply here.

Comment by wizjany

As of 5.x, this can all be fixed by removing all the build flags and adding an owner (can be anything, doesn't have to be a real player) to the global region. Not sure if you're referring to the new 6.x versions though...
The build flag has never interacted with player damage (mobs, falling, pvp, whatever).

Comment by sk89q

No, it works on 5.x because I learned that if you add members to a region, it completely overrides BUILD=DENY on a lower priority region. Since I "fixed" that inconsistency in 6.x, how the reporter (and possibly other people) have been using the BUILD flag kind of broke.

The build flag now covers player damage too. And doors. And dropping sand into a region.

The USE flag will override BUILD in the latest builds though. I had changed it for 6.x so it wouldn't do that anymore but some other people were relying on old behavior so I changed it back.

So I need to figure out whether I will revert it to previous behavior or what.

Now I need to either:

1. Change it back.
2. Add "DISALLOW" state (weaker than ALLOW and DENY
3. Add a "wilderness" region.
4. Have people add members to the global region but I find this really hacky.

Comment by sk89q

#The latest WG 6 build changes it back to WG 5 behavior so that a region will override BUILD=DENY, so that should fix your problem #1 and #2.

#See #1

#To allow PvP, use {{/rg flag global pvp allow}}. This is because if, for example, you want to protect someone's home, you probably don't want people to come into that person's home, kill him or her, and take the stuff, so PvP is disallowed. However, in your case, because you aren't protecting the area for that reason, you want to allow PvP everywhere.

#I plan on adding a configuration setting so you can list blocks that are not protected at all so you can add doors to the list. That OK?

Comment by TNTUP

Ok thanks!

For the PVP flag, okay, so monsters will still attack players despite the BUILD=DENY?

Yeah, if you can add this, that would be nice

Comment by sk89q

PvP flag should not be affecting monsters, so monsters should still attack, I think. I might have to double check.

Comment by TNTUP

I did tests, still in BUILD=DENY in global that mobs doesn't damage out players, I thought it would be in the player's region instead. I tested with a region and a sub-region that works as intended. Player A owns the region, Player B owns the sub-region in PlayerA's region that PlayerB cannot modify PlayerA's region and PlayerA cannot modify PlayerB's sub-region.

I guess for the door use flag isn't implemented in the config I guess.

Sorry for my bad english. Used WorldGuard 6 #1422

Ill do more testing later, thats I've found since the update ;)

Comment by sk89q

I made separate tickets: WORLDGUARD-3172, WORLDGUARD-3159

Make new tickets for each issue if you can.

Comment by TNTUP

Okay, thanks, will do that in the future