luck perms is not compatible with a plugin
broken1arrow opened this issue · 10 comments
Description
I have not set any player perms or group perms, but by default all perms is on true on veinminer. No problem if i use ultra permissions (i have copy in same perms for hand) And i not set any perms for veinminer in any groups.
Reproduction steps
Yes i done several steps and get help on DC.
this is only part of perms player shall not have access too, players get access too all veinminer commands
https://luckperms.net/verbose/YruRTYJpWn
No player not op, he cant use /plugin,/version or /reload
Expected behaviour
Shall not have access too all commands.
Environment details
Pappermc 1.16.2 184
LuckPerms version: 5.1.93
Any other relevant details
I have ask on veinminer, but i think is more a LP issue.
When i look on it, it give player /veinminer mode, /veinminer toggle /veinminer version but not /veinminer reload.
And all of veinminer perms, i think players get this some how, ultra permissions can block this for player use some how. I think you need add something to LP, some block all perms from get use if I not add it to perms.
veinminer.veinmine.*
veinminer.toggle
veinminer.mode
Looks like a miss configuration. You have perms set to true directly for the user, which will be prioritised over perms inherited from group. And this spins also why you are experiencing perm being true even if it's not set in any group. The issue you face not due to a incompatible or a bug.
Looks like a miss configuration. You have perms set to true directly for the user, which will be prioritised over perms inherited from group. And this spins also why you are experiencing perm being true even if it's not set in any group. The issue you face not due to a incompatible or a bug.
Yes i know, it way i use a other player some not have admin group and only "luffare"
Seems to be so in any case with these two plugins, so perms are handled quite differently and it is not easy to know what is a bug or user error.
But may put perms on false in the group and see if the person who makes the plugin can change a bit (because on the server it is not so good to give everyone access to all tools directly).
I simply have to watch out for this in the future in the plugin I add.
Yes i give glizh_ perms, but it was for testing it on an account that does not have staff perms
https://luckperms.net/editor/QZTa4Ru1yn
Looks like the player you're testing with has that permission from somewhere. Run lp user <name> permission checkinherits veinminer.toggle to see where it's coming from. If it returns undefined, run /lp editor and send the the link.
User uuids aren't private and can be found by simply googling their names. Send the link
User uuids aren't private and can be found by simply googling their names. Send the link
Seems to be misconfiguration then, not a bug :)
Depends a lot on what you are used to how prems also work.
In any case, it seems to be quite different between these two plugins (one allows some defualt perms others do not even allow these). So not only "misconfiguration", the error is how different these two plugins I compare work with perms.
Do not know if you get a warning if you transfer the plugin data from another perm plugin to your normal one as well.
Have a plugin that you could not support, so have not been able to test.
But can not be the only perm plugin that blocks all perms by default, even those plugins issue normally