LuckPerms

LuckPerms

41.4k Downloads

not every permission listed in tab autocomplete (essentialsX)

Blighthorn opened this issue ยท 8 comments

commented

I am using EssentialsX 2.0.1 (Build 578) base+antibuild+chat+spawn.
Luckperm tab autocomplete suggests only few permissions:
*, fly, gamemode, mail, motd, sleepingignored, spawn-on-join, speed, teleport

theres a LOT permissions missing here.
On Build 571 it was ok, but I wanted to add antibuild and upgrade. Maybe permission list grows too much?

Once I had all the list, I restarted server and joined game to check several times but cannot reproduce proper behavior.
Now there is only short list all the time.
At server start there are no error messages about essentials or LP.
I am using Vault too.

commented

I have downgraded essentialsX to build 488, removing all addons - but still the same...
Strange, because before it was ok. Seems, like list of permissions is not properly collected by vault or LP. I don't know what to do.

commented

Interesting finding, after I use command like /home then in the autocomplete list appear .home and .sethome
I am now puzzled.

commented

Luckperm tab autocomplete only applies to lp/lpb commands. Not to essentialsx commands.

Wrong issue tracker.

commented

Hey, the issue is not about autocomplete commands, but permission nodes.
Like essentials.home or essentials.worlds.(worldname) etc.
It takes place during /lp group (group_name) permissions set ____ (type main node like essentials then dot and TAB for possiblities)

commented

Did you actually read the wiki?
https://github.com/lucko/LuckPerms/wiki/Command-Usage#lp-tree

The tree is built using data exposed to the server by plugins, and expanded over time as plugins check for permissions.

Tell me how is Luckperms able to tell what a perm node is unless it does a check for it? By "magically" guessing - which will be a danger in on itself. Or by node checks being performed - as outlined in tree

commented

Ok, thx for answer. I thought that all persmission nodes are known as plugins are enabled at server start, and not exposed in time. That was because I always saw all permission nodes for other plugins, and I am pretty sure sometimes I saw all for essentialsX too. Usually long list is what I git, thus I thought that maybe now there is something wrong, not then, beacause I upgraded LP to newest version not long ago. That's pity, because that autocomplete is one of main reasons I use LuckPerms, to list nodes without looking for them in web and always get correct spelling. If you are interested, here is my tree. I also remember to get some autocomplete nodes for some plugins by doble dot (like pluginname..permnode), but not now. So the only exception where I don't have whole list is EssentialsX now.

commented

Found work-around. After /help it seems that Essentials perform checks for all permissions, and then the tree is complete tree.

commented

Yeah, since EssX doesn't register it's permission nodes via the plugin.yml when loading, they'll only appear in the tree / tab-completion once they've been checked for at least once since the server started.