WORLDGUARD-3708 - Reported by andrewkm

Original bug from here:
https://www.ecocitycraft.com/forum/threads/access-denied.151956/#post-849030

Looks like all regions with interact:deny took a dump. Reverted back to 1670 and all is well.
On 1672 players couldn't open their chests, doors, nothing.

One region was fixed by setting interact to allow and then back to deny.

Problem is somewhere here:
77cd257
or
22e5e8a

Did you change how interact works completely or something?
Is there no conversion available from old to new format?

I'm confused what's going on. For now will stick to 1670.

Comment by wizjany

did you actually just put highly experimental dev build onto a production server?
top kek.
that said, neither of those commits should actually change the behavior of any existing flags, and there is no "new format" for anything.
additionally, that's exactly the behavior i'd expect with interact set to deny.
that's literally what deny means.

Comment by andrewkm

1670 works fine, 1672 doesn't work at all.
Something clearly changed with the interact flag.

Comment by wizjany

interact deny is working fine for me, as is every combination of member/nonmember X allow/deny/none.

http://i.imgur.com/2YgVWrM.png

Comment by wizjany

k i looked at the thread since you neglected to mention a lot of things in this report, and i found the relevant issue:
https://www.ecocitycraft.com/forum/threads/access-denied.151956/#post-848968
interact-group and use-group have never been valid flags in worldguard. whether in 1670 or 1672 (or 6.0 or anything else), the correct output has been "interact -g NON_MEMBERS: DENY".

so no clue how you got those flags in there.

Comment by andrewkm

Ok.
A region with:
flags: {interact: deny}
Means those NOT part of the region shouldn't be able to interact with stuff inside, while those IN the region should be able to right?
Or did this change?