WORLDGUARD-3636 - Reported by zera_fox

I've been using WorldGuard 6.1 for some time now and have found that many flags are not working properly.
First, I cannot get Owners or Members gamemodes to change when entering regions. Secondly, there appears to be an issue with the Interact flag as well. I have child regions within parents that have different interact permissions but the children are ignored, despite the settings being different.
I've given regions that needed, priority settings over others, still no change.
The Greetings and Farewell don't exactly work either, and are rarely spotty at best.

Comment by wizjany

you probably just need to set the group flag for gamemode if it works for nonmembers but not members

i am not sure what you mean by the child regions getting ignored - if the regions are overlapping you should only be using priorities, child regions have nothing to do with that.

and greeting/farewell seem to work fine, you are going to have to make a better bug report if you think there's something wrong.

Comment by zera_fox

It doesn't work for anyone, the gamemode...

I've done priority and I've tried child. Neither have worked in allowing my members to access the chests of the region that is overlapping Spawn. And yes this smaller region has a higher priority.

I don't know what you're wanting from me other than telling you what's going wrong. I don't have errors, I don't have anything more to give you than what I see.
If you don't believe me, I can provide you access to my server with full WG permissions to see it for yourself.

I don't know what else to do.

Comment by zera_fox

room_2:
    min: {x: -113.0, y: 75.0, z: 859.0}
    max: {x: -111.0, y: 80.0, z: 861.0}
    members:
        unique-ids: [df520247-84f2-4a5b-9f2b-3d950d3ad01a]
    flags: {interact: allow, interact-group: MEMBERS}
    owners: {}
    type: cuboid
    priority: 99
spawn:
    min: {x: -154.0, y: 0.0, z: 826.0}
    max: {x: -100.0, y: 255.0, z: 881.0}
    members:
        unique-ids: [19a3e9ac-6b6c-42eb-bfd7-725d547dd404, 4b3304b9-27b4-41bb-8f08-a5eeb20fb3e0,
            c5f6851b-b336-4a91-a5d4-b4bcc952a23e]
    flags:
        game-mode: CREATIVE
        blocked-cmds: [/lock, /unlock]
        greeting: ยง6Welcome to Spawn!
        interact: allow
        enderman-grief: deny
        game-mode-group: MEMBERS
        mob-spawning: deny
        fire-spread: deny
        farewell: You are now leaving Spawn!
    owners: {}
    type: cuboid

Is this perhaps more helpful? Room 2 is where we noticed some issues, so it's the one I've been trying to tweak here and there to get it to work.
Similar Regions like
room_3:
min: {x: -110.0, y: 76.0, z: 846.0}
max: {x: -108.0, y: 79.0, z: 851.0}
members: {}
flags: {interact: deny, interact-group: NON_MEMBERS}
owners: {}
type: cuboid
priority: 1

Still allow anyone to access the chests and doors...

There is nothing wrong with my flags or my priorities, so I cannot for the lift of me figure out what's wrong.
This whole version has done nothing but give me struggles from the start, but up until now I had my fingers crossed a newer update with solutions were in the process/being pushed out. I was horribly wrong, obviously as you can find nothing wrong on your server(s)..

Comment by wizjany

you have some very odd flag setups going on here...can you explain what exactly you're trying to accomplish? from what i can tell, you have a bunch of chests/doors throughout spawn that you want everyone to be able to use, but you also have room* regions within spawn that you only want members to be able to interact with chests/doors in. is that correct?

Comment by zera_fox

Yes, essentially there is an INN built at spawn, and we have no reason to not allow everyone to use the Main Door or any other door located at Spawn.
However players are able to rent these 'rooms'/regions via another plugin and become members. These regions however are intended to stop the use of doors and chests to everyone except owners/members of the region.

Except for some reason it's not working. Once a Member is added to the room region, the member can no longer access the door/chests inside, but can still interact with other room regions and spawn doors, etc;

And I have tried to flag the room regions with both "Interact Non-Members DENY" and of course "Interact Members Allow". But neither make a difference.

I think they worked once upon a time when Spawn wasn't allowing anyone to interact with doors, but that proved to be a problem for everyone and players were complaining. Which left me with this dilemma.

Comment by zera_fox

Any suggestions on what I may be doing wrong here? :
I've never had so much trouble with WG before.