WORLDGUARD-3382 - Reported by LegitRedStoner

I'm terrible at explaining issues, but I will do my best, I have also created a video to accompany my issue.

Issue: When a region has the flag "build deny" a user cannot access any blocks, ranging from enchantment tables, to anvils etc. Although they can use chests.
Here's the video: http://youtu.be/RtSvz56q_F4
NOTE: Chest access is set to "none" so it doesn't have any effect.
Thanks for your time.

• Aaron.

EDIT:
Players can NOT interact the following:

• Beacon
• anvil
• enchantment table.
• enderchest
• door
• cauldron

Players CAN interact the following:

• Chest
• brewing stand
• dispenser
• dropper
• hopper
• jukebox
• furnace

World guard version:
http://i.gyazo.com/b0f5476befa98d0e95de40524d3d2eb0.png

Comment by LegitRedStoner

@wizjany Are you using world guard 6 beta 5?
Also the passthrough flag acts exactly the same as the build deny flag.

Comment by wizjany

Try the latest build from http://builds.enginehub.org
And no, they don't act the same.

Comment by LegitRedStoner

@wizjany In the version i'm using, they do :/

Comment by LegitRedStoner

@wizjany I just downloaded the latest one, (2 days old), same exact issue.

Comment by wizjany

clear all your flags and so on and try setting up the regions again. if it doesn't work, pastebin your regions.yml file.
also stop using build deny.

also, do users get a message when they attempt to interact with a chest?

Comment by LegitRedStoner

UPDATE:
Issue fixed, apparently there's a "interact" flag with wg 6.x ._.

Comment by wizjany

The behavior of the build flag should be the opposite. Chests (any any other container) should be interactable while things like enchantment tables should be allowed.
I suggest not using build deny however. If you want to prevent building globally, set passthrough to deny. As for your specific issue, I would guess you are running an old version of worldguard or you have some other flags set somewhere, setting build deny is working as expected for me.