-
Notifications
You must be signed in to change notification settings - Fork 121
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
Comments
are you able to provide example configs? this sounds like a misconfiguration somewhere or a bad implementation of groups on LWC's end. |
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. |
Using permissionsbukkit 2 Yes, this work if you use LWC only without any permissions wrapper like Vault. It could be like: 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: All is fine while there is no Vault and LWC talks directly to PermissionsBukkit. |
Well, getGroups fail as well when using Essentials/GroupManager while Vault or other wrapper is installed. |
Take a look at Jenkins #761 |
Very nice. It fixed the getGroups issue. |
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.
The text was updated successfully, but these errors were encountered: