Groups not recognised

I'm having a strange issue with groups. Whenever I add a group to a region using "/region addowner/addmember SomeArea g:Admin" It does not work, the people in the group are not recognised as owners/members. It works perfectly well when I add people by their names.
I'm using permissionsbukkit.

I know this might have been answered already, but I can't seem to find the answer anywhere.
Thanks.

same problem here, no error in console

I'm having the same exact problem! I am using GroupMangaer with GM Bridge and most other plugins work fine, but WorldGuard seems to have a major issue. E.G. /region define spawn g:admin gwner doesn't work at all. I remember in previous versions it did, but alas it fails. I don't think this WEPIF idea is helping a whole lot.

Add a group node permission to each permissions group. (eg. group.regulars)
I'm using PermissionsBukkit and this works.

I tried adding group.groupname nodes under PermissionsEx and didn't seem to have much luck.

It also occurred to me because of group permission inheritance, i would end up adding quite a lot of negative nodes, and then even potentially reordering the group entries in the file to be children first topdown because in PEX negative nodes must occur before a positive one in the file in order to override.

In the end i just reverted back to a WG build from 11 Dec and groups work fine without changing anything.

If you're using group inheritance then that's how it's supposed to work. You don't need negative nodes. (eg. in situations where a player is in the moderator group, he'd have group.moderator, group.regulars, and group.default; then he'd have permissions in all those regions that has any one of those groups as owners/members, as expected) You'd only need negative nodes if you for some reason didn't want higher tier permissions groups access to lower tier permissions groups' regions. But if you're in that situation, maybe you should re-evaluate inheritance or how you're using WG. I can't imagine a logical application of that. It would cause unnecessary headaches for many situations.

I have group inheritance and the latest dev WG and everything works wonderfully.

we have a beginner creative area where only the lowest ranked groups may build. Through inheritance all main groups would then qualify for this area.

I guess the alternative would be to drop the inheritance from this group but then loose the ability to /pex promote.

I have no problem with adding ~20 lines to the permissions file, simply pointing out a nuance in how the new method operates.

I still don't understand how to use these child and parent nodes and stuff. I just want to say that in my bpermissions, guests can only build in a set location, but be able to tour the rest of the map. The only way they can build outside of the guest area is if we promote them in bpermissions to a higher rank. Do I have to use permissionsbukkit?

Just make guests a non-inherited group or use a negative group node in the first group to inherit guest permission nodes.

Okay, but where do I add the build.guest and build.builder nodes, will they work in bpermissions?
So assuming that everything works, I would add the build.guest node under the guest permissions. Then in game I want to NOT allow them to build in the __global__ region. I want them to build in a specific region called "guestbuild" that is inside the __global__. So what would I do so that our Guests can ONLY build in "guestbuild" but they are allowed to tour the rest of the server, while allowing anyone ABOVE guest to build anywhere?

What? Those nodes have nothing to do with WorldGuard, so I don't know what you're talking about.

Like you said, prevent anyone from building in __global__ except people above guest. Then make a region where guests are members.

That is exactly what i'm confused with. Like how do I do that? Do I have to do any configuration with my bpermissions or can I just leave it as is and do everything in game? And how do I make guests members of an area because i tried /rg addmember guestbuild g:guest and all it gave me is "expecting a player".

I'm going to have to make a FAQ for this forum, lol. I guess the wiki is lacking in this particular area, because it keeps coming up. Read here first to see if you understand: http://wiki.sk89q.com/wiki/WorldGuard/Regions/Introduction

As for how to do what you asked, try this:

- Add "group.groupname" permission nodes for each group.
- Create large region (or __global__, but that acts a little differently, so it'll require testing)
- Add "g:membergroupname" as a member of large region.
- Add "g:guestgroupname" as member of smaller guest region
- Give smaller region higher priority than larger region

(don't put these in verbatim. each group name is specific to your configuration)

For the larger region, I want to use the __global__ region. Do i need to set any flags or anything for it? Like do I need to create it?

Like I said... testing...

Try what I said. (except the second line, since __global__ already exists)

Thank you, I will try that and report back.

Okay so I have the smaller region set up by using /rg addmember guestbuild g:guest.
Then when i try to do /rg addmember __global__ g:builder, it says can't find a region by that ID

That's weird, I just tried it and it works. Maybe you need to modify a flag first just to get __global__ into the region file. That's the only thing different that I did. Either that or you mistyped "__global__".

Okay, Ill try modifying the global PvP flag

It worked
Thank you so much!