Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LWC getGroups returning empty or inconsistant list while using vault or other permissions wrappers #395

Closed
leagris opened this issue Oct 9, 2012 · 7 comments

Comments

@leagris
Copy link

leagris commented Oct 9, 2012

When LWC is running the permission check through that. Their implementation it can return no groups and PermissionBukkit will always return at least default.
On disabling Vault, LWC registers the limits correctly.

IF you are trying to make private doors so only certain groups can have access, you type in:
/cprivate g:Builder enter
and it say it worked.
but a member of the Builder go to the door and it tells he cant open the door.

@Hidendra
Copy link
Owner

Hidendra commented Oct 9, 2012

are you able to provide example configs? this sounds like a misconfiguration somewhere or a bad implementation of groups on LWC's end.

@leagris
Copy link
Author

leagris commented Oct 9, 2012

This is my setup with PermissionsBukkit config.yml: http://pastie.org/5024412

I indeed declared nodes with group.groupname to be able to use group access control inside Worldguard regions with the very same syntax as supported by LWC: g:groupname

If I put LWC in debug. Without my patched version, I clearly show no groups at all because it tries to get do the getGroups with Vault.

@Hidendra
Copy link
Owner

Hidendra commented Oct 9, 2012

What group are you in, and are you using PermissionsBukkit v2.0?

When I added myself to the Animateur group and used /lwc debug, I'm shown every inherited group

This is on the latest build of LWC

@leagris
Copy link
Author

leagris commented Oct 9, 2012

Using permissionsbukkit 2

Yes, this work if you use LWC only without any permissions wrapper like Vault.

It could be like:
/perm player setgroup hidendra Citoyen
/perm player addgroup hidendra Oziria

Usually, registered players get promoted into Citoyen (as main group) and them they choose to join a given city group like Ozira as secondary group.

A member of Oziria may choose to restrict a chest in the wild to allow only members of his own city group with:
/cprivate g:Oziria

All is fine while there is no Vault and LWC talks directly to PermissionsBukkit.
But as soon as Vault is installed/enabled, it fails.

@leagris
Copy link
Author

leagris commented Oct 9, 2012

Well, getGroups fail as well when using Essentials/GroupManager while Vault or other wrapper is installed.
I switched from GM to PermissionsBukkit some weeks ago because GrouManager had some annoying short-comings about properly managing per-world permissions I did not want to cope with.
PermissionsBukkit is my prefered permissions plugin (same team as CraftBukkit, consistent intelligent, easy to maintain).

Hidendra added a commit that referenced this issue Oct 9, 2012
@Hidendra
Copy link
Owner

Hidendra commented Oct 9, 2012

Take a look at Jenkins #761

@leagris
Copy link
Author

leagris commented Oct 9, 2012

Very nice. It fixed the getGroups issue.
Tested it on my server and it doess its job just right. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants