WORLDGUARD-3289 - Reported by Simon.Teague

So I just updated to the latest beta, and even tried the latest dev, but all interactions with passive mobs, crafting tables and enchantment tables seem to be disabled by default? This is a pretty major bug. Surely this type of interaction should be enabled by default.

I'm sure it effects other items as well, these are just the ones I've come across.

Comment by Simon.Teague

In the case above sorry it's for a global region. On things like a survival/factions server certain things like PvP need to be enabled/disabled globally. But I'm guessing enabling the interact flag globally would cause unnecessary flags to be needed for child regions. Maybe disable this logic just for the case of global regions?

Comment by sk89q

OP is talking about "by default" -- by default, nothing is protected.

So I'm confused as to what the situation is here.

Comment by Simon.Teague

So in summary:

If you create a global region named GLOBAL, this by default disables all interactions. Is this intended?

Comment by sk89q

No. That shouldn't happen and does not happen for me.

By "create," I also assume you mean by setting a flag on it, because you shouldn't be able to create global with /rg define.

Comment by Simon.Teague

@sk89q Yes, I mean when you set a flag on it.

I'm running the latest dev version of WG and when I do say '/region flag GLOBAL pvp deny', all interactions with things like enchantment tables are now blocked globally. Is there a config option causing this, or is this a situation you haven't tested?

Comment by sk89q

Can't reproduce.

Please use {{/wg debug testinteract}} on block as illustrated here:
http://docs.enginehub.org/manual/worldguard/latest/commands/#troubleshooting

If you still have the problem, post your regions.yml and the output of {{/wg report -p}}.

Comment by Simon.Teague

@sk89q So I just did as you said.

If I type '/wb debug testinteract normalplayerusername' when selecting a crafting bench, I get a message saying 'No plugins cancelled the event'.

I have this config for the world I'm in:
http://pastebin.com/5JhbUhyy

This is the result of '/wg report -p':
http://pastebin.com/raw.php?i=6YCcK83z

Any ideas what on earth is going on? I mean I only have WorldGuard, WorldEdit and PEX running. So it can't be another plugin causing it.

Comment by sk89q

Is it spawn protection?

The report says:

Protection: Spawn Radius: 16```

Comment by Simon.Teague

@sk89q This isn't within spawn protection. It's a good 50 blocks away. Without the global region defined everything works correctly.

Comment by Simon.Teague

Might it be related to me running Spigot rather than Bukkit?

Comment by Simon.Teague

@sk89q Just one thing to note is that this only effects passive mobs, not aggressive ones. Which is what initially led me to think that it was a bug.

Comment by sk89q

If you uninstall WG, does it still happen?

Comment by Simon.Teague

@sk89q No, without WorldGuard or with the INTERACT flag set to true on the global region users can interact with things. This only happens when I set a flag on a global region such as pvp. So the global region exists, but doesn't have any flags related to interacting.

That's the issue. By default, INTERACT is set to deny on global regions - where it should be set to allow.

Comment by sk89q

Sorry, but I cannot reproduce using a (1) brand new server install using (2) a 2-4 day old version of Spigot with the (3) latest WG dev build:

http://pastebin.com/raw.php?i=hhRe9UEY

Comment by sk89q

I noticed that {{BuildFlag{name='build'}: DENY}} is set on your global region in your report, though your other link says that you don't have any other flags in your global region.

While I don't know which one is correct, I'm inclined to believe the report. Having build=deny protects the entire world against nearly everyone and everything (pistons included).

Comment by Simon.Teague

@sk89q Have you tried with the exact settings I had on my global region?

So:
global:
Type: GLOBAL
Priority: 0
Owners: {players={uuids=[], names=[]}, groups={names=[]}}
Members: {players={uuids=[], names=[]}, groups={names=[]}}
Flags:

Rather than just:

global:

One of them might be the cause.

Comment by sk89q

Didn't make a difference: http://pastebin.com/raw.php?i=gFYWwH0F

Second, the global region you are pasting is '''not''' the global region for your main world -- it's for your '''nether''' world. The global region for your main world is:

	Regions: 
		Region Count: 8
		__global__: 
			Type: GLOBAL
			Priority: 0
			Owners: {players={uuids=[], names=[]}, groups={names=[]}}
			Members: {players={uuids=[], names=[]}, groups={names=[]}}
			Flags: 
				StateFlag{name='creeper-explosion'}: DENY
				BuildFlag{name='build'}: DENY
				StateFlag{name='leaf-decay'}: DENY
				StateFlag{name='pvp'}: DENY
				StateFlag{name='mob-spawning'}: DENY
				StateFlag{name='vine-growth'}: DENY
				StateFlag{name='enderpearl'}: DENY
				StateFlag{name='fire-spread'}: DENY
				StateFlag{name='potion-splash'}: DENY
				StateFlag{name='enderman-grief'}: DENY```

Comment by Simon.Teague

@sk89q So a user on your server - someone that isn't a member of the global region and doesn't have admin worldguard perms - can interact with things correctly? Are you testing this with a user rather than someone with WG admin perms? If so I'll just set the INTERACT flag to true on all global regions, because this is getting silly. :p

Comment by sk89q

As you can see with my report, I don't have a permissions plugin installed. I don't ''use'' a permissions plugin when I develop. I obviously had no op when I tested it.

I am pretty sure it's because you're confusing your nether world for your main world, because you keep giving me pastes of your '''nether world''', while I suspect you're having this problem on your '''main world'''.

Comment by PseudoKnight

I'm pretty sure what you're talking about isn't a bug. It's the new interaction protection in 6.0 that was recently moved to the "interact" flag. Members can still interact with those things. If you want non-members to interact with those things in regions, then you'd have to modify that flag. It's possible it still needs some design changes, but it's not a bug.

The upgrade doc actually covers this and many other notable changes pretty well.
https://github.com/sk89q/WorldGuard/blob/master/UPGRADE.md

Comment by Simon.Teague

@sk89q This effects all global regions sorry, irrespective of world. I just tested in the nether because that had less default flags.

Comment by klebe

Same issue here: global flag is set to passthrough deny so players can only build stuff in regions they own or where the passthrough flag is set to allow. Nonmember users can interact with doors, anvils, enderchests just fine even on other users' regions. However they can't interact with workbenches or enchantment tables in the global region or user regions they aren't a member of.

I even tried to simply put [workbench, enchantment_table] into the interaction-whitelist line but that didn't change anything at all.

Comment by sk89q

Well, that's a different issue. This ticket is about a fresh install of WorldGuard with just a global region created (no flags changed).

In your case, can you make a new ticket?