Bukkit

@JackVanDyke

Might.

@Androkai

I didn't check yet what WG6 does...

The problem with the stuff WGPFix monitors (pistons, flow, grow), that you don't always have a "you", in terms of "who started it", but you do have the owners and members of the affected regions. Thus there certainly is a couple of variations for what to allow, e.g.:

• Allow everything (old WorldGuard with flags not set + config).
• Allow nothing (old WorldGuard with flags set + configs).
• Allow if combined members+owners names match up for all affected regions (WGPFix).
• Allow inside of one region only (Not sure if done anywhere - still quite rigid, but better than turning off globally, probably WG6 does this?).
• Allow cross-region if all owners names match (more rigid than WGPFix - this variation probably doesn't make sense by itself).

How safe things are, depends on if/how safe adding/removing owners is. For instance WGPFix will pop the pistons that violate cross region constraints, which helps a lot against potential exploits. It's still thinkable to claim a region next to tze to-be-griefed region, and add the same owners + members as the other region (only oneself is extra) - then you build the griefing base (lava etc) and you remove your ownership, putting the griefing setup to work. That's actually a good reason to prevent any cross-region stuff, despite it being quite rigid. Not sure what can be done against it, other than preventing dropping ownership (other than by transfer through sales). Towns with container-region usually are ok i guess.

Some variations would be dangerous, e.g.:

• Allow if at least one owner matches for all affected regions (problem: You can add the other regions owner just for griefing...).

@Androkai

Blocking pistons isn't the point of this plugin :p - WGPFix cool feature is to ALLOW cross-region stuff ONLY if owners+members match.

Sure the first thing people think about is blocking pistons from outside, but WGPFix does in addition enable you to use pistons across your grounds (and grow trees and fluids). Does WorldGuard do that too now, or does it just allow to block pistons fully?

@Androkai

Oh :) - i have not yet had time to verify that, i think it would explode as of now. I will have a look into that too, however i have to adapt my whole plugin-eco-system to WorldGuard 6 then, which might or might not be a trivial task and could take a while. But i will start more testing on that soon.

@Androkai

WorldGuard 6 seems to change a couple of things, not sure i can work with that yet (might break lots of plugins). Eventuelly i will update to use that.

@DosMike

Depends much on WorldGuard... could be that it's already compatible with WorldGuard future changes, because "same owners and members" would work the same way with uuids [Edit: strings...], however i am not sure what WorldGuard will look like internally.

@yannick_diepart

One could add a configuration option to confine further. I allow this, because it usually does not pose a threat to let players change the "wilderness" from their region as base.

Question is why do you need this? Do you have building denied in the global region?

If you need to deny building, in theory a workaround could be to set a container region that covers all the map with an owner like "$SERVER" and a priority of -1.

@Tetdoss

2.2.0 pending approval - i hope this fixes it!

@CHRONICALSde

I'll discuss on the pm thread :9.