primary-group: is not taken...
CloudeLecaw opened this issue ยท 4 comments
inside my player files i have the setting
primary-group: admin
But the player does not get the permission of admin
This only happen if i add admin to the parents...
parents:
- admin
- player
i thought parents are the thing other called inheritance:....
this is since the migration of the permissionsex database
LuckPerms_5.1.93
I'm not sure quite what you're saying. If you're trying to say setting the primary group to something doesn't take affect unless you add the group to parents, yes, that is how it should be.
By default you shouldn't need to touch the primary-group, it should be automatically calculated based off of weight.
i tried aggain with the latest version 5.2.18 from the luckpermsweseite :)
ok so:
i migrated the dabase from permissionsex to LuckPerms
This is how my playerfile looks after --(i chose the yaml storeage)
uuid: f24df990-9c6b-4f32-938a-4c91a26d31f4
name: Cloude_Lecaw
primary-group: admin
permissions:
- gadgetsmenu.suits.frog.*
parents:
- spieler
now when i log in im still counting as player until i add the group admin to the parents
after added admin to the parents it works
so i changed it to
uuid: f24df990-9c6b-4f32-938a-4c91a26d31f4
name: Cloude_Lecaw
primary-group: admin
permissions:
- gadgetsmenu.suits.frog.*
parents:
- admin
- spieler
then it works.
So the question was why the primary group is not the group i am in
or do i have to add all primary groups (i specect these where the groups they where in PEX before)
to the parents of the players that have other ranks?
Or are the parents the same like the inheritance: in PermissionsEx? - whatmeans a group get all permission of inherite all permisions of the defined group if no other permissions set in the group - Example: VIP got the inheritance of PLAYER in Pex
Yes, that's correct behavior*. If a user doesn't inherit from a group, it can't be their primary group. As stated in my above comment, the primary-group should be automatically calculated without admin intervention.
*If the first example is what our /lp migration spat out, then perhaps there's a bug in the PEX migration. That's a different issue.
tl;dr this is working as expected.