LuckPerms

LuckPerms

41.4k Downloads

Parent nodes buggy

John-H-Smith opened this issue · 8 comments

commented

Given a default group which has the permission "essentials.spawn" and a group user which has default as parent, sometimes the user group is not permitted to execute /spawn due to insufficient permissions.

Server version: git-Spigot-56f8471-43183ea
LuckPerms version: 5.0.23
Essentials version: 2.16.1.216

commented

So you set essentials.spawn to the group default?
Did you make sure you're using EssentialsX (Not Essentials. The X is important!) with EssentialsXSpawn?
Also, what is the actual MC version itself? The git version of spigot doesn't give a real clue about that.

commented

Yeah, default group has permission essentials.spawn.
Yeah, I am using EssentialsX with EssentialsXSpawn.
Server is on version 1.14.4R01.

This only affects some users. I have multiple players in the user group, some can execute the command, some not.

commented

I think I may be running into the same issue. If not, let me know and I'll open a new one.

I have 3 groups:
default
member (parent: default)
mod (parent: member)

default has essentials.*: false
member has essentials.(sethome|home|me|msg): true

I am currently set as "mod", but when I try and run /home, I get "You do not have access to that command."

Running /lp verbose gives me the following output: (copied from web, sorry for the formatting)

t3rminus | essentials.home | false
Context: world=world
Origin: PLATFORM_PERMISSION_CHECK
Processor: me.lucko.luckperms.common.calculator.processor.WildcardProcessor
Cause: match: essentials

This set-up definitely worked in v4.4, but it's not working now that I've updated to v5, for some reason.

Server version: 1.15.1-R0.1-SNAPSHOT git-Paper-25 (MC: 1.15.1)
EssentialsX version: 2.17.1.29
LuckPerms version: 5.0.23

commented

Could you try using the verbose command to debug this a little further.

https://github.com/lucko/LuckPerms/wiki/Verbose

It should make it clear what's going on here.

commented

@t3rminus I suspect 88c4324 will fix your issue.

commented

I found my error. I migrated from permissionsex and there I used another group as default then 'default'.
So the user group inherited the old group and not the 'default' group.

commented

@t3rminus I suspect 88c4324 will fix your issue.

Is there a new or replacement syntax that I should be using instead? I’m fine to upgrade from legacy syntax if necessary.

commented

@t3rminus I suspect 88c4324 will fix your issue.

Is there a new or replacement syntax that I should be using instead? I’m fine to upgrade from legacy syntax if necessary.

No need :)